Running a Moto X 2014, XT1093, with cm-13.0-20161122-NIGHTLY-victara, no custom kernel, with Xposed v87. Have SuperSU installed from Play Store, and ever since I tried updating the su binaries from stock, after upgrading from cm 12.1, I only get infinite boot until I reflash the rom, as that, I presume, overwrites the newly installed binaries. Is there a problem with the binaries? A compatibility issue with Marshmallow that I missed? Or is this some sort of unique issue?
Related
Just flashed android 6.0, the latest release of it for the Nexus 6.
Installed TWRP and Root and custom kernel Despair to be exact. However, Xposed doesnt work.Tried installing it with a zip file.
Also, since it doesnt install correctly, end result is stuck at boot.
Nevermind, figured the issue out.
FYI for any future issues, Selinux must be set to permissive.
I must chime in and say, that's not a necessity...
I'm running almost the exact same basic setup (only difference is kernel, I got FK) and Xposed is working fine with selinux set to enforcing.
I had xposed install and active on my motorola x pure phone which is running marshmallow. I received a message one day that there was an update for my moto x pure, and before I thought I clicked on install and ended up in boot loop.
I flashed a saved version of my rom which was prior to installing xposed. My processor is an arm64. When I attempted to install v85 again, I noted that on the screen it mentioned that 'no md5 file was found' and the process ended in like 10 seconds. When I rebooted my phone and tried to install xposed it said there was no framework installed.
So I tried to the framework uninstaller, wiped cache/dev and then tried to install the framework again but no joy ( I have also tried v81, 83 as well but get the same result).
I wanted to see what thoughts others may have. Thank you ahead of time.
Seems like your phone is back up and running, just no Xposed framework is activated.
Try downloading the Xposed zips through your browser and installing it. See if the results are different. That's the only thing that I can come up with.
Also, when you say you flashed a saved version of your ROM, did you dirty flash, or did you restore a nandroid backup?
Sent from my Nexus 6P using Tapatalk
Sorry I flashed a backup I created through twrp
Sent from my XT1575 using Tapatalk
I am having an issue installing xposed-v87-sdk23-arm.zip with the recent dailies of CM 13. It seems to happen no matter the CM daily or version of Xposed(v85/v86/v87). All it does is get stuck during boot and causes the battery to heat to ridiculous levels. I end up having to reboot into recovery and flash the Xposed uninstaller and this allows the phone to boot.
I'm not sure if this issue is Xposed based or TWRP based as when I install SuperSu and attempt to update the binary using TWRP I get the same thing, stuck during boot and hi-temp battery. In this case I reflash the last daily and this fixes it.
I have tried just about every variation of installing/wiping dalvik/cache(or not) and rebooting I can think of but always the same results.
Any further information or directions to look in would be appreciated.
Sent from my DROID Turbo using XDA-Developers mobile app
You read this that I posted in the CM13 thread, right?
http://forum.xda-developers.com/showpost.php?p=69637739&postcount=223
ChazzMatt said:
FYI for anyone running Xposed modules:
http://forum.xda-developers.com/showpost.php?p=69636994&postcount=875
Click to expand...
Click to collapse
CM13 made security changes which cause bootloops with xposed. Xposed V87 is supposed to fix that. You definitely do NOT want v85/v86.
At this point have you uninstall xposed framework entirely (using the uninstaller file), and booted in CM13 successfully? Only after doing that would I then attempt to re-install xposed (v.87, or newer for future readers) and any modules.
You mention TWRP. Not sure how that would be involved, but are you on the newest version?
twrp-3.0.2-0-Mod_04-quark.img
https://www.androidfilehost.com/?fid=529141701856462150
I'm on Resurrection Remix 6.x for all Quark which is based on CM13 (Marshmallow). I am using xposed v87 with three different modules on that ROM. If you can't get CM13 running successfully, perhaps switch to RR 6.x as a test -- even temporarily? You have TWRP, so you can make a backup...
(When I switch to a new ROM, I let Google Play restore my apps. Then I use Titanium Backup to restore data only to user apps that need it (Nova launcher, email apps, etc), but not to restore any system apps. It's relatively painless, just takes a little time. Titanium Backup remembers all the configurations, passwords -- and you are not switch OS versions, you would still be on Marshmallow, just a different ROM.)
It's possible it's something else besides the November security patches. How long have you had this problem?
Thanks for the reply ChazzMatt, I had not seen that, thanks for sharing.
As I said, I have tried most any uninstall and reinstall combo possible, including completely uninstalling using the uninstaller.zip and reinstalling as normal. Same issue.
I bring up TWRP because I have seen previous issues with it, such as not being able to decrypt partitions even with the correct password. I was not sure if this was another such bug in TWRP.
I have been having this issue since November, so it could very well be something related to the security update you mentioned.
Sent from my DROID Turbo using XDA-Developers mobile app
I have successfully installed Magisk on my device Root works but when I try to install a magisk module I get an error about not being able to mount magisk.img. When I try to install through recovery the module is flashes without any errors but once you open the app It displays "no modules installed". Before the G5s plus that I have a had the Moto G5 Plus. It had the same problem I just had to install another kernel over stock one and Magisk would work as expected. Is there a kernel for stock room that would support Magisk. Anyone else had this problem or is it just me?
ive no issue installing modules through magisk. Theres a lot of factors here. You didnt mention but id presume you installed magisk through recovery. Also, I presume you installed xposed. Maybe the modules your using require xposed to work. I forgot the exact steps to install xposed through magisk, but its not hard, and Id assume anyways you tried all of that. Have to flask xposed through recovery if I remember, then you can install xposed app apk too through recovery, then open magisk and install the latest xposed there. Im not using a stock rom, however Im fully confident if you properly rooted, and unlocked your phone of course, (I assume you did, just saying) its not a kernel issue. Sorry if I wasnt any help, its all i can think of right now.
When I got the phone I unlocked the bootloader and installed TWRP. When I set up my device I went back to recovery to install Magisk 14.3. It installed correctly and I got root using Magisk but when I try to install any module through the Magisk app I get an error. If I got you right should I try to install Xposed too? I was planning to install Xposed, Magisk version. But when I try that I get an error. I have attached a screenshot of when I try to install Xposed by topjohnwu and Greenify for Magisk. I get the same error.
well, xposed may not be your issue if you cant install any module with magisk manager. The modules, majority of them, if not all of them, i dont know, do not require xposed. Some do, most do not. Now please keep in mind, i could be wrong. I would say this, no harm in installing xposed, its basically a must get anyways for many awesome apps/modules. How you install, first install the xposed manager, youll have to look around for it, its not on the play store. Then downkoad magisk xposed through magisk. Once you download that zip file boot into twrp and install xposed through twrp.
This is a youtube on it: https://www.youtube.com/watch?v=MCcvsOp83A4 Now thing is, this may not fix any of your problems. But theres a chance it may. Like i said either way you want xposed on rooted phones anyways.
Patched kernel for stock. I have no problem running modules on Magisk. Flash in recovery.
https://forum.xda-developers.com/showthread.php?p=73930507
Sent by way of magic
if youre using stock rom, try this kernel. i just compiled it today from geneticengineers git. last updated hours ago.
Ae3NerdGod said:
if youre using stock rom, try this kernel. i just compiled it today from geneticengineers git. last updated hours ago.
Click to expand...
Click to collapse
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
Ae3NerdGod said:
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
Click to expand...
Click to collapse
Is there a thread for these kernels or any for G5S Plus?
THERAJ12 said:
Is there a thread for these kernels or any for G5S Plus?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g5s-plus/development/kernel-t3707143/post74562730#post74562730
wifi fixed btw
As the title says, I'm always getting bootloop after installing Xposed Framework on my lg g6. I clean-flashed my device several times, but no success. Also didn't install other things like Magisk or SuperSu, I flashed the phone, did the normal "first startup" - **** and then directly flashed Xposed.
Tried Versions of Xposed were 88 and 89. Tried Software builds were 11i and 10t. Also tried LineageOS and it worked, but I don't want to use a custom rom, honestly. Please help.