Got my 5x for Christmas. I immediately unlocked and flashed TWRP, and started playing with ROMs. Once I settled on cyanogenmod, I decided to flash xposed. After flashing it, upon boot I got stuck in a loop of "Unfortunately, NFC service has stopped." errors.
Since then, I have been troubleshooting on the factory image. I formatted everything, even the sdcard, and then flashed the factory image. I then booted, then flashed and booted TWRP.
From this point, I have tried, in every order imaginable, flashing SuperSU (systemless and traditional), flashing xposed, and installing the Xposed Installer apk. No matter what I do, I get the NFC error loop. I have also tried both xposed v78, v79, and v79 dirty flashed over v78.
The only thing which has been even mildly successful has been flashing the original 6.0 factory image and then following the above steps. This results in a working xposed installation, but then upgrading to 6.0.1 and reflashing xposed causes the loop again.
From what I can tell by reading here and on /r/nexus5x, plenty of other people are having this issue, and no one seems to have the actual cause or solution. So please, if you have seen this issue, post the circumstances (be as specific as you can with versions, orders, etc), as well as your personal solutions. And if anyone has the true cause and/or solution please post that as well.
Deleted
gpvecchi said:
Deleted
Click to expand...
Click to collapse
v78 doesn't work for me either. I've seen a number of people mention that v79 causes this error, and that reverting to v78 will fix it. However, I cannot get either v78 or v79 to work.
lpreams said:
v78 doesn't work for me either. I've seen a number of people mention that v79 causes this error, and that reverting to v78 will fix it. However, I cannot get either v78 or v79 to work.
Click to expand...
Click to collapse
I just clean flashed mmb29q, tried to install v80, and got the nfc bootloop. Only way to fix was to flash the xposed uninstaller.
Tried this: checking "Enable su during boot" in the SuperSU app, then reflashing Xposed. No luck.
And nfc was not on prior to flashing xposed the first time.
Xposed v79 worked for me fine on mmb29p.
I used supersu 2.66 on mmb29p, and 2.67 on mmb29q.
Busybox installed?
Disabled NFC in settings first before flashing xposed
I got this too on MMB29Q with NFC enabled in settings. I disabled NFC in settings prior to flashing on the next try and flashing xposed v80 worked fine. After installing xposed framework, I was able to turn on NFC in settings again and all is well.
Go it to work. This was my path: Checked every box in SuperSu Settings tab that wasn't checked (e.g., enable multi-user, enable su during boot, etc.), installed the Xposed apk, flashed Xposed zip in TWRP.
Setup: MMB29Q, TWRP 3.0, SuperSU 2.67
I have the same issue trying to use layers manager. Wonder if it's related
I've installed v77 all the way up to v82, all with the same result while also trying everything mentioned before
UPDATE: I've checked literally everything now, including multi-user (didnt think that was necessary before), everything works now on v80
Sent from my Nexus 5X using XDA-Developers mobile app
Related
http://forum.xda-developers.com/showthread.php?t=3074586
I had been using it for the last 2 days with out any problems.
Same here!!
But when I install Smart Alarm Icon & XInstaller at the same time ,and I reboot to see if the two Xposed app works.
However, I got stuck on the boot screen.
Yet, I haven't tried to install each app at a time, so I dunno which app caused the problem...
jasonlee0315 said:
Same here!!
But when I install Smart Alarm Icon & XInstaller at the same time ,and I reboot to see if the two Xposed app works.
However, I got stuck on the boot screen.
Yet, I haven't tried to install each app at a time, so I dunno which app caused the problem...
Click to expand...
Click to collapse
I was running it on ARHD but got some weird ram overflow..
It just stacked my 3GB completely full untill the phone became unresponsive so I had to restore a nandroid to fix it..
Weird issue, it might have been one of the modules..
Just waiting till official 64bit version comes out I think...
Hi all
Would like to install exposed, any news on the 64bit version and or the bugs mentioned?
Cheers
blocka said:
Hi all
Would like to install exposed, any news on the 64bit version and or the bugs mentioned?
Cheers
Click to expand...
Click to collapse
If you are using 5.1 can find all info here, If you want to use Install xposed-v70-sdk22-arm64-by-romracer-20150808.zip is what you need and you can get the APK here
If using 5.0.2 use link in OP
thanks liam_davenport
I've been looking for a guide or instructions on how to recover from a boot loop but haven't been to successful in finding anything worthwhile. So wanted to ask here, if it does happen (not that it will) I just want to cover my bases and know beforehand how to recover from a boot loop. Obviously part of the recovery process would be to have taken a NAN backup prior to installing the xposed framework, to recover it's a process of booting into recovery and restoring the NAND?
Really looking forward to getting this on my phone.
Thanks guys.
There is an uninstaller zip available, flash it when you experience a bootloop ( http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 ) . Otherwise just flash your rom new, that works as well. Then deactivate all your modules and start reactivating them one by one, you might have an incompatible module running,, which causes it
I've not gotten this to work so far. I'm on 5.1 stock rooted, s-on. Booted up successfully after installing the zip, but when I launched Amplify it says xposed isnt active.
When i went to check in xposed, it says romracer 71 active though. A little help anyone?
Sent from my HTC One M9 using Tapatalk
neverborn said:
I've not gotten this to work so far. I'm on 5.1 stock rooted, s-on. Booted up successfully after installing the zip, but when I launched Amplify it says xposed isnt active.
When i went to check in xposed, it says romracer 71 active though. A little help anyone?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Did you activate the module?
I did, yes. However, it does seem like Xposed just won't work with stock 5.1 / odex / S-OFF; bootloops abound.
I've resorted to ARHD 12 to get it to work.
neverborn said:
I did, yes. However, it does seem like Xposed just won't work with stock 5.1 / odex / S-OFF; bootloops abound.
I've resorted to ARHD 12 to get it to work.
Click to expand...
Click to collapse
It does work with rooted stock 5.1 s-on though. Sometimes it requires the 2 button reboot. It occasionally sticks at the splash screen but not often. I have used Greenify, Sense Toolbox for Sense 6 and 7 (which has lots of cool features like 12 mini quick toggles and status bar and notification hiding), Always Correct for password memory on my keyboard, YouTube Ad Away, X Hangouts which allows custom theming and features and YouTube Background Playback.. All working great here with the Romracer sdk22 arm64 5.1 framework zip and Xposed Installer 3.0 alpha 4
Sent from my M9 using Xparent Gray Tapatalk 2
Thanks for letting me know. On the other hand, i can stick with ARHD as it's been so stable so far.
Sent from my HTC One M9 using Tapatalk
There is an official 5.1 x64 version now..
oemfoefoee said:
There is an official 5.1 x64 version now..
Click to expand...
Click to collapse
True that, just flashed...first boot was not successful or maybe I wasn't patient enough but the second boot went fine..all working great.
I've installed the latest (v73) official xposed for android 5.1 over romracer's unofficial one and didn't have any issues. First boot, all good! All modules works great..
Same here all works fine
Powered by SkyDragon ROM
Ask working here in Leedroid with screen off animation and gfe
I can't get it to work. I installed the xposed.apk from the link http://forum.xda-developers.com/showthread.php?t=3034811 which is version 3 alpha 4 and then flashed the framework in TWRP, which is the xposed-v75-sdk22-arm64.zip file. I have an HTC One m9 running android 5.1. When I reboot, it shows that "version 75" is installed in xposed but when I try to run any xposed requiring app it doesn't work. For example, MinminGuard says "Xposed is not enabled".
Is there ANYTHING I can do??
Veraster said:
I can't get it to work. I installed the xposed.apk from the link http://forum.xda-developers.com/showthread.php?t=3034811 which is version 3 alpha 4 and then flashed the framework in TWRP, which is the xposed-v75-sdk22-arm64.zip file. I have an HTC One m9 running android 5.1. When I reboot, it shows that "version 75" is installed in xposed but when I try to run any xposed requiring app it doesn't work. For example, MinminGuard says "Xposed is not enabled".
Is there ANYTHING I can do??
Click to expand...
Click to collapse
Did you enable the module? Go to Xposed app - Modules - Click the tick boxes - Reboot
Yeah the modules were already enabled. I ended up finding what was causing the problem. I had to go into Super SU and change default access to "Grant" and checked the "Enable su during boot" box. That finally made it work.
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
Hello guys
I'm experiencing the following issue:
I am trying to install the latest Oxygen OS update on my OP3 (talking about 3.2.8). I can do so and at first it works fine, but as soon as I activate Xposed (not the framework itself, that's no problem at all. It's appearently ANY module that needs to be activated) the booting process doesn't finish and I get stuck on boot-animation-screen. Has anybody experienced the same issue or even found a way to fix it?
Also, the Xposed Uninstaller ZIP doesn't seem to work on the OP3. It failes. And any time I want to try again I need to restore a hole Nandroid. Is that a known (or fixed) issue?
Here's some backround info:
- It's not just my phone, same issue on my sister's
- Root and Xposed framework themselves are no problem. Issue starts when activating any Xposed-module
- Xposed worked flawlessly on previous version
- I tried it several times
Would really appreciate any feedback, even just if it's a known issue!
Thanx
What xposed version are you using?
Use xposed v87 , it will work fine then
Or you can try the systemless xposed.
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
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for