My Z3 running 5.0.2 reboots during app installs or uninstalls. I thought i could live with it but its become extremely annoying now.
I have xposed running with the latest fixes applied. Is it likely to be caused by this?
I don't know how to disable xposed at this stage or i would have tested this.
Any advice?
Forgot to mention I'am rooted with LB.
I
Related
I just pushed the new 4.4.4 update for my Droid Ultra (not Dev edition)
Fortunately, it kept root access! Unfortunately, no matter what I do, the Xposed framework is refusing to work now. I've had it running flawlessly with 4.2.2 and 4.4, but now it'll download and appear to install, but it keeps asking me to reboot even after I flash it or do the "classic" installation.
Is anyone else having this issue?
You kept root but lost the ability to write to the system. Have to wait for a write protection exploit
Ahh okay! I get it. Hope one gets released soon!
So if 4.4.4 retains root would I be correct in concluding that in spite of that the WPNoMo/Pie combo technique from the bounty thread for 4.4 still won't get us a root that survives reboot/wp-off due to the new security in this update?
mmarsh665 said:
I just pushed the new 4.4.4 update for my Droid Ultra (not Dev edition)
Fortunately, it kept root access! Unfortunately, no matter what I do, the Xposed framework is refusing to work now. I've had it running flawlessly with 4.2.2 and 4.4, but now it'll download and appear to install, but it keeps asking me to reboot even after I flash it or do the "classic" installation.
Is anyone else having this issue?
Click to expand...
Click to collapse
When xposed asks you to reboot just cancel and choose soft reboot. Any time you do a hard reboot you will lose the xposed framework. If that happens just re-install the framework and do a soft reboot.
Hey guys, I'm a pretty heavy tinkerer and I know that comes with some risk. But before I completely wipe and reflash everything I wanted to see if someone could help diagnose my problem.
I have a Nexus 5 and have been running MultiRom for a while. I currently have Paranoid Android and Android L dual booting. I was on the newest version of PA (4.6 BETA 1) but I just flashed back to a past backup so now I am on PA 4.4 (I think). I have been having random reboots for about a day and now I can't even get my phone to stay on longer than a few minutes. I just installed Xposed and a few Modules so I assumed those were giving me the trouble, but I uninstalled Xposed when I started having problems and that didn't help. Even my backed up ROM and my Android L won't work without rebooting. This leads me to believe its something deeper down than my ROM.
Before I clean off and reflash, is there any way I can diagnose or fix this issue?
Thanks a ton.
So, all is well here, the .244 update came and it is smooth as hell, only problem is that xposed is terrorising me.
I installed every .zip xposed files possible for 6.0 and 6.0.1 all giveing me bootloops after i restart the phone...
At first i thought it was a module causing the problem, i had wiped my phone clean several times... Still...
Please help...
It did work fine for me, no issue at all... (with latest xposed v85)
can you share the zip pls
http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v85-sdk23-arm64.zip
thx, but i have found the problem. Apperantly the problem was in the kernel, i flashed the one that came with the ftf a user shared, after i flashed androPlus's kernel everything was normal
So I updated my newer Shield Tablet to 4.1, and restored everything, flashed SuperSU and Xposed and Viper4Android.. It was working fine until I enabled some Xposed modules and rebooted. It gets stuck on the NVIDIA logo and nothing happens. I got it to boot once after flashing Xposed, but the app said that Xposed was installed but not enabled ("see the logs," which made no sense to me). It said there was an update to the app, so I updated it, then downloaded the zip once again and flashed it, and got the NVIDIA logo stuck again. This is horsh!t. Why is it suddenly not working? I'm using the latest, xposed-v85-sdk23-arm zip.
Bump? Been a day and no response??
GuyInDogSuit said:
Bump? Been a day and no response??
Click to expand...
Click to collapse
Maybe nobody knows HERE?
Xposed is working here with NVIDIA-Update 1.2 (6.0.1) without problems. Did the modules you installed work before the update? A bootloop is a common problem with Xposed.
I doubt that this is ROM problem but an Xposed problem. I would try to find help in the Xposed section. Maybe you should try to find the logs...
edisso10018 said:
Maybe nobody knows HERE?
Xposed is working here with NVIDIA-Update 1.2 (6.0.1) without problems. Did the modules you installed work before the update? A bootloop is a common problem with Xposed.
I doubt that this is ROM problem but an Xposed problem. I would try to find help in the Xposed section. Maybe you should try to find the logs...
Click to expand...
Click to collapse
No, it's a ROM problem. They worked fine before.
I'm also using the 6.0.1 update and the latest xposed with no problems. I'd say it's one of your modules not being compatible, not a ROM problem at all, except that the module doesn't seem to be updated to work on mm.
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
I'm also using the 6.0.1 update and the latest xposed with no problems. I'd say it's one of your modules not being compatible, not a ROM problem at all, except that the module doesn't seem to be updated to work on mm.
Click to expand...
Click to collapse
I use the same modules on my phone running 6.0.1, with no issues. It's not a module.
did you flash arm version or arm-64 version? cuz arm-64 and intel wont work and there is a systemless xposed try using that if all else fails. I can use xposed myself on 6.0.1 myself btw.
m666p said:
did you flash arm version or arm-64 version? cuz arm-64 and intel wont work and there is a systemless xposed try using that if all else fails. I can use xposed myself on 6.0.1 myself btw.
Click to expand...
Click to collapse
As I stated in the op, it's the xposed-v85-sdk23-arm zip.
Tried reflashing the ROM, the USA LTE version this time, and I'm STILL getting stuck at the boot screen, after enabling modules. I got it to boot with JUST Xposed, no modules.
GuyInDogSuit said:
Tried reflashing the ROM, the USA LTE version this time, and I'm STILL getting stuck at the boot screen, after enabling modules. I got it to boot with JUST Xposed, no modules.
Click to expand...
Click to collapse
As stated before, a module your using isn't updated to work with our implementation of 6.0.1. now reinstall modules one at a time until you figure out which one is causing problems and then ask in the xposed section for that module. Glad you finally figured it out tho
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
As stated before, a module your using isn't updated to work with our implementation of 6.0.1. now reinstall modules one at a time until you figure out which one is causing problems and then ask in the xposed section for that module. Glad you finally figured it out tho
Click to expand...
Click to collapse
Well, it was BootManager, but it's working fine on my phone with 6.0.1.
Nope, wasn't BootManager, either. Just not working, at all.
Hello,
Since I have unlocked my Bootloader and installed an Custom Kernel I have sometime's Sleep of death. So I must hold the Powerbutton and Vol Up to restart. Has anyone an idea and can read the Logfile?
https://drive.google.com/file/d/0B7iBahEWKKQ_VG1BYmtpSHg5OGM/view?usp=drivesdk
-Happy Feet- said:
Hello,
Since I have unlocked my Bootloader and installed an Custom Kernel I have sometime's Sleep of death. So I must hold the Powerbutton and Vol Up to restart. Has anyone an idea and can read the Logfile?
https://drive.google.com/file/d/0B7iBahEWKKQ_VG1BYmtpSHg5OGM/view?usp=drivesdk
Click to expand...
Click to collapse
i didn't look through he log, but i had a similar issue before, and it was related to systemUI.apk, i was using a faulty systemUI.apk, and what fixed it was to restore the original one ...
so if you're not using a different systemui than the one comes with SliMM (like Xperia X systemUI) maybe it's some app or a mod or an xposed module that's interacting with the systemUI.apk, i suggest to 1st make sure you have the original SystemUI and then disable anything that's affecting it or modding any of it (modifying status icons or navbar...etc) ... this may be the issue.
Thanks for reply. I flashed the advanced stock kernel and anything is smooth again. I flash this Elitekernel again and disable, Uninstall xposed and look what happens.
Good morning, I Uninstalled xposed and this was the Problem.
-Happy Feet- said:
Good morning, I Uninstalled xposed and this was the Problem.
Click to expand...
Click to collapse
I've had the same problem,i think it's because of elite kernel,now without kernel modified only slim 3.1 everything is back to normal,and i dont use xposed anymore.
Xposed sometimes causes more issues than the benefits it offers
kansasboy001 said:
Xposed sometimes causes more issues than the benefits it offers
Click to expand...
Click to collapse
I have blocked some services with Amplify. That was the Problem.
Did you undervolt it or disabling cpu hotplug? It may being power suspend or device going to very deep sleep causing important services stopped or postpone like *backup* or *alarms*
I'm already experience with some custom kernel on my previous Xperia Acro, Xperia Z and now Z3 that incompatible between custom kernel, ROM and xposed are relatively can cause SOD, just check latest log