Related
Greetings all..
I am working on the Not e 4 and run a large collection of Xposed mods
I have a Sprint Note 2, Note 3 and Note 4 and the 2&3 have never given me any issues with Xposed Framework Modules.
The frame work
Several are causing boot loops upon reboot.
The device will not boot into safemode- which is a huge pain if you did not do a backup in recovery.
I just wanted to remind everyone that if you install Xposed ( and ignore all of the "make sure you nandroid/ backup first messages) this time REALLY MAKE SURE YOU BACK UP /System at least before you activate mods.
I will post a list of the ones giving me issues shortly as I work out process of elimination.
Do you have an idea why my phone says "updating" after I install Xposed?
It's not stuck or anything but in the status bar it has a logo with a checkmark and I have no service. Am I supposed to freeze something?
I don't use many xposed modules and don't have boot loop issues with the ones I use. My problem is not all options in Wanam works. Like disabling sound waning when putting the volume too high. Hopefully the Wanam devs will fix that.
gfp11289 said:
Do you have an idea why my phone says "updating" after I install Xposed?
It's not stuck or anything but in the status bar it has a logo with a checkmark and I have no service. Am I supposed to freeze something?
Click to expand...
Click to collapse
If you turn off Software Updates from the ApplicationsManager you wont see it anymore.
xxSTARBUCKSxx said:
If you turn off Software Updates from the ApplicationsManager you wont see it anymore.
Click to expand...
Click to collapse
I turned off Software Uodates and it still comes up in the notification bar
I don't get any service either upon installing and restarting with xposed
When you installed xposed installer (assuming this was not from a titanium backup), it should have saved a zip file called, Xposed-Disabler-Recovery.zip to your sdcard or internal memory.
Install it in recovery and it will disable xposed framework so you can figure out which module is not working.
Here's a link:
http://www.datafilehost.com/d/ccb18d00
Deleted. Thanks. ^^^^^^^^
hermeticist said:
When you installed xposed installer (assuming this was not from a titanium backup), it should have saved a zip file called, Xposed-Disabler-Recovery.zip to your sdcard or internal memory.
Install it in recovery and it will disable xposed framework so you can figure out which module is not working.
Here's a link:
http://www.datafilehost.com/d/ccb18d00
Click to expand...
Click to collapse
I'll try it when I get home
I just install this in TWRP?
gfp11289 said:
I'll try it when I get home
I just install this in TWRP?
Click to expand...
Click to collapse
Yes. It removes xposed framework without uninstalling anything.
This way you can use the process of elimination add to which xposed module is screwing up your system:
Reinstall framework, turn one module on at a time, reboot, repeat.
If you are sure individual modules are not messing up, don't bother turning them off.
hermeticist said:
Yes. It removes xposed framework without uninstalling anything.
This way you can use the process of elimination add to which xposed module is screwing up your system:
Reinstall framework, turn one module on at a time, reboot, repeat.
If you are sure individual modules are not messing up, don't bother turning them off.
Click to expand...
Click to collapse
The thing is that I didn't have any modules on. I just installed it, updated it, rebooted, and I'm stuck with no service until after I uninstall it
Weird
Maybe I could try to flash Xposed in TWRP? If that's even possible..
gfp11289 said:
Maybe I could try to flash Xposed in TWRP? If that's even possible..
Click to expand...
Click to collapse
All you have to do is install the apk. Then once in Xposed, install the framework.
Id try uninstalling the framework, deleting the apk and download a fresh apk of xposed and start fresh. Dont associate TWRP with installing Xposed.
I think its working now. For some reason the update stays on my status bar for awhile before it turns off by itself. I tried to send myself some text messages last night and they took a long time to send, or just never sent at all. I have some decent status by my house so that wasn't an issue. I might've not given my phone enough time to boot up xposed or something, but regardless it's working now.
Being connected to wifi, does in anyway affect sending text messages while I'm on xposed? I barely had enough time to test it out when I was at home but driving around my city I was sending myself text messages and they seemed to go through okay.
Wanam Xposed
11/5/14 Wanam Xposed Module update available.
Drama!!! It is just Xposed Framework.
I just bumped my lollipop rom and install xposed then I noticed that my phone shows out "android is upgrading" on every reboot. Is there any way to fix this as it is a little annoying...:crying:
Sorry for my broken English
+1 !
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' is better than, well you know.
kp_q said:
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' and better than, well you know.
Click to expand...
Click to collapse
This activity tends to get lengthier after every reboot. I've found that once it "seems" to loop in the "Android is upgrading" screen, to remove the battery, boot into recovery, wipe the Dalvik cache, and reboot. It will go through the lengthy procedure of updating software, but will boot a WHOLE lot faster after that.
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
alqoshi4life said:
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
Click to expand...
Click to collapse
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
abbey666 said:
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
Click to expand...
Click to collapse
Which Xposed version did you use? I'm on v68 right now which is the latest. I had v67 and it did the same thing.
V66. I tried2 later versions but this one worked for me.
I have a Oneplus One but I have the same issue. Every damn boot. Android is starting. optimizing app 1 of 121.
I also have the latest version of xposed.
I know not the forum for the OPO but just thought I'd let you guys know other phones face it too and hopefully find a solution to this.
I had to make a really important call and my phone restarted all on its own. That's bad enough but add to the random restart sitting for 5 minutes to wait for android to finish optimizing
abbey666 said:
V66. I tried2 later versions but this one worked for me.
Click to expand...
Click to collapse
I tried v66 like you recommended and the same thing happened. So it must be something else that solved your problem. I guess I can live with it though.
have the same problem with my g3.. everybody have data backup ? )
BlackGodRaven said:
have the same problem with my g3.. everybody have data backup ? )
Click to expand...
Click to collapse
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
alqoshi4life said:
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
Click to expand...
Click to collapse
l solved it too ) l transfer backup to sd card )
abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
Trying this now...my G3 crashes for whatever reason from time to time after my Tasker that disables bluetooth as soon as the USB power is disconnected from the car.
Currently on version 79. Patched it with Lucky Pater and removed all odex; rebooted (got stuck but battery out & booted normally).
I'll report if there are any further issues
Okay it's very odd it seems like there's an issue with my LG G3 disconnecting bluetooth from the stock head unit in '13 WRX. If I try pushing the power button off on the radio then shut off the engine (Tasker shuts down bluetooth) then I don't seem to have this issue with the phone crashing. I've yet to have the phone crash if it's on A/C power and Tasker performs the same function.
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app
I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.
Looks like Magisk 14.5 might have something to do with it.
Starting on page 452 there are a few posts from there on about it.
Symptoms are a random reboot with a soft boot loop of the SystemUI. The only way to correct it is to hard reboot the device.
I can usually go a few days worth of up time between the bug reappearing.
I was the exact same way on 8.0. Every couple of days, it would start randomly rebooting and/or apps would start crashing. The only fix was to hold the power button until it rebooted. Rebooting by just pressing the power button and selecting reboot would always hang.
I was hoping 8.1 would fix it, but it's quite a bit worse. It's done it at least 4 times so far today. Same symptoms. Apps will start crashing (sometimes the foreground app, sometimes background ones), or the phone will just soft reboot, or both. Sometimes it's while I'm using it, sometimes I'm not using it at the time. No rhyme or reason, that I can tell..
I had one app that crashed immediately every time I tried to start it until I uninstalled it and restored it from backup (with data). That was weird.
If this keeps up, I may have to roll back to 8.0.
theycallmerayj said:
I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.
Click to expand...
Click to collapse
There is a larger thread on this HERE. There is no definitive smoking gun yet but certain root apps seem to be causing it. One way to rule out Magisk would be to simply uninstall the app temporarily (longpress>>App Info>>Uninstall) then fastboot flash the original boot.img and dtbo.img. Run this way long enough to know for sure whether being rooted is causing the issue. There are tons of people rooted who do NOT have this issue, so it is more than likely one of your root apps/themes is causing it.
Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.
theycallmerayj said:
Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.
Click to expand...
Click to collapse
Have you tried Adaway? I use very few root apps, but that is the first one I add every time. I've not had any reboots at all and it is very effective. Because you only use the one root app, you may find the culprit was UH, and not Magisk.
I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots
theycallmerayj said:
I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots
Click to expand...
Click to collapse
You can use different host files you don't have to use the ones that come with AdAway. Try Steven blacks out
I'm having this same issue with Magisk. I experienced it with an older Magisk on 8.0 as well.
I'm thinking about just getting rid of Magisk altogether. However, I used ES File Explorer to edit my build.prop to add the command to disable the nav bar. I'm nervous that uninstalling Magisk will cause the "your system is corrupt" message and a bootloop. However, I also have Flash Kernel installed. I wonder if the custom kernel will allow me to use the phone with the modified build.prop and without Magisk...
Hi all,
I have installed Magisk 16.0 based on Maik93's post, and Xposed Framework SDK27 90.2-beta3 (Systemless), through Magisk modules.
When I enable the Xposed module, the phone first shows endless boot animation, and when restarting it again, it boots, but the Xposed app seems not installed (not listed in Settings->Apps and its icon is not present in chooser), although, in Magisk, it is visible in the Modules and it's checkbox is checked.
Did anybody successfully installed Xposed with A2 Lite? What can be the problem?
Thanks a lot,
Circum
Did you install the apk of xposed?
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
https://forum.xda-developers.com/attachment.php?attachmentid=4393082&d=1516301692
Here is the link from xda
No, sorry, I was not aware that it is a separate thing.
Now I have installed, but it says that no Xposed Framework is installed. If I try to install a framework from inside the installer (90-beta3), it -- obviously -- reports an error that /system/framework/XposedBridge.jar already exist...
Because of this, I cannot enable any module from Xposed Installer.
Any tips what do I do wrong?
I want to use Xposed too but we will have to wait for TWRP I guess.
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
mik.y said:
I want to use Xposed too but we will have to wait for TWRP I guess.
Click to expand...
Click to collapse
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
HoangP05 said:
You can install now through Magisk if you want, if yiu get bootloopbfor any xposed module, just flash thr original boot.img
Click to expand...
Click to collapse
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
mik.y said:
I was able to install it somehow,but stuck after each reboot in process. Now some apps are diying like call enhancement and some test app. So its quite dirty. I have Magist 16.0 installed.
Lol,I cant connect to internet with xposed to download any module. Useless
Click to expand...
Click to collapse
Not all are working apparently, but if it is bootloop, you so try to let it boot again, press power and volume down as the same time while it bootloop, the second boot always work for me
There is TWRP for Mi A2 Lite.
Search on google.
NOTICE: For now there isn't official TWRP. There'w unofficiak fork which can you install using fastboot. :good:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
HoangP05 said:
Not sure what happened to you, did you tried ti reboot your phone? Mine is working just fine
Click to expand...
Click to collapse
Xposed's Gravity box module works on Mi A2 lite?
Yes, GravityBox is working, although as I mentioned, there are issues with boot - I have to reboot several times until it succeeds...
performace drops significantly when i install the xposed module for magisk. i hope they fix it.
So far everything works fine on my end, I'm not noticing any performance drops in my day to day use. Then again I haven't used it much without Magisk + exposed but from what i'm seeing it's working well, no noticeable lag or stuttering.
I have gravity box, Amplify and Greenify modules running.
circum said:
Not sure what happened, AFAIK I have rebooted the phone at least once, but after rebooting again, it said that the framework is installed, but has some problem with it and not functioning (yellow background, sorry, I forgot to take a screenshot), and rebooting once again solved the problem, I can confirm that Xposed works.
But as others mentioned, installing Magisk itself makes problems with the boot. Booting always stucks, I always needed (even before installing Xposed) to long-press power after several minutes and the second try usually boots up.
Now having Magisk and Xposed (and GravityBox) installed usally need to restart booting twice (i.e., the 3rd boot works).
Any suggestions how to debug / get logs about this problem?
Click to expand...
Click to collapse
Magisk alone didnt give me boot problems. What rooting guide did you follow?
fake__knv said:
Magisk alone didnt give me boot problems. What rooting guide did you follow?
Click to expand...
Click to collapse
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
circum said:
I used this one: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
But before the update. Since that I have removed Magisk to enable the OTA update, and did not put it back yet -- although, there are many small areas I feel the lack of root...
Click to expand...
Click to collapse
I can assure you @BubuXP's guide is good. Used his rooting guide, followed the steps for updates and its good to go. I rooted my phone when Im on August update. Now Im in September update