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
Related
I have tried many versions of Xposed, from the newest down to version 18 I think it was, but the further back I went, the worse it got. The framework installs fine each time (for each version tried) according to the message within the Xposed app.
Basically I cannot find a working version of the xposed framework for my N9005 Note 3, it's not carrier branded apart from the boot animation, there are no carrier apps at all, it's almost entirely stock.
I still have it running the original 4.3 Jelly Bean. Baseband N9005XXUBMI6
On the newer versions of Xposed, I get no signal and it makes the phone a bit laggy, and various other things misbehave. On older versions approaching and including 18, I started getting looped force closes on Android Media, Bluetooth Share, Contacts & Messages (which didn't go away after uninstalling xposed), and the options in the top of the pull down took ages to activate and toggled themselves on/off. I uninstalled each Xposed version, then wiped the xposed cache & data before final uninstall (before trying a different version) each time. And I also did the reboots after installs as recommended.
Only thing I've done to the N9005 is root (of course), superuser, TWRP (recovery) and using TSF launcher, and I don't think these last 3 would be triggering a clash/problem.
Was really looking forward to using some Xposed modules but for now I had to restore my backup from when the phone worked. I see other people with Note 3s (maybe other models) working Xposed fine, just wondering if the Xposed team can help by supporting the N9005 or telling me that I'm somehow doing it wrong. (or anyone else who can help).
Thanks
hummm, i can almost see someone asking for a logcat
Sent from my LG-D805 using XDA Free mobile app
On same phone. Never had any issues on any rom with Xposed. Try another ROM. I run Crashrom kitkat.
Have anyone succesfully got Xposed Framework running on stock 5.0.2 L90 D415??
I think you have to get a new recovery (twrp) in order to install xposed and then install the rom again.
Correct me if I'm wrong.
I flashed the zip file, wiped cache, and reboot. My phone booted up but i got com.android.phone force closing. Weather app also force closes. And since com.android.phone force closes you get no signal.
My experience...did the lollipop ota for tmo, didn't really care for it much. Used one click root, added flashify and twrp custom recovery and did a nandroid backup. Installed xposed arm zip and it just stuck on the lg logo for quite a long time. Second attempt i did the wipe after installing xposed and it made it past lg logo to tmo boot and hung up. In my reading, saw something about xposed will not work on stock firmware. But isn't xposed for people that want to mod stock roms? Main thing is...back up before anything. Have already used mine 4 times.
So I originally flashed the latest xposedv66 and was not successful. Found xposed-arm-20150213b.zip everything looked good, even had signal. Like you, weather app stopped. So, I tried file manager to get to the installer and it stopped also..
If you're going to do it, BACK UP BEFORE YOU INSTALL. I cannot get it to work, reason why? I do not have the logs but if you install liveboot and activate it, then install the zip and reboot, liveboot will show you a command that is supposed to activate but fails and retries. Its essentially a bootloop but without the reboot. It will not allow you to boot without that feature being activated. Do it for yourself but remember to back up all system partitions and restore them. When you reboot after restore, the system will do the whole 'optimizing apps 1 out of 200' thing so don't worry if it takes a while to boot. Will have more on this when I get home to my laptop.
Xblackberryuser said:
So I originally flashed the latest xposedv66 and was not successful. Found xposed-arm-20150213b.zip everything looked good, even had signal. Like you, weather app stopped. So, I tried file manager to get to the installer and it stopped also..
Click to expand...
Click to collapse
Can you share that xposed? Because im trying to find one that works and can only find latest version..
Enviado do meu LG-D405 através de Tapatalk
Warimation said:
Can you share that xposed? Because im trying to find one that works and can only find latest version..
Enviado do meu LG-D405 através de Tapatalk
Click to expand...
Click to collapse
Here you go.
Found another one from March and April, but I haven't tried them.
Xblackberryuser said:
Here you go.
Found another one from March and April, but I haven't tried them.
Click to expand...
Click to collapse
I tried the one you suggested and I successfully rebooted. However, Lollipop ran slower and then I opened the alpha apk that came on the official thread. It said alpha 3.0 was installed but not activated. So I just decided to restore to before I installed. Xposed is being worked on and its in its alpha stage. Its bound to have bugs. Since THE D415 already has root, I'm fine to wait for an official version of Xposed that works to come out. Also, Even though I had 2 Gigs of data left on internal, there was a notification pestering me saying there was little to no storage left on my phone. Otherwise, no app crashes.
jesuita said:
I think you have to get a new recovery (twrp) in order to install xposed and then install the rom again.
Correct me if I'm wrong.
Click to expand...
Click to collapse
Flashing the ROM again will only wipe/remove xposed.
It's a known fact that lg weather doesnt work on xposed lollipop i also found that file manager didnt work during my period of testing, i don't know if i experienced com.android.phone force closing since I restored from my backup but xposed is definitely not usable on stock lollipop.
Newest xposed version v68 works great! No phone FCs. Now go download it!!!
Where can I download the newest version at because all of them up to this point are not stable on my lg 90 415d , I tried v71 and everytime I try to open my gmail Google Play services force closes
Sent from my LG-D415 using XDA Premium 4 mobile app
jbonilla51 said:
Newest xposed version v68 works great! No phone FCs. Now go download it!!!
Click to expand...
Click to collapse
Weather app, File manager app works on Lollipop D415 no problem or still buggy with some apps but fixed some others?
krchi said:
Weather app, File manager app works on Lollipop D415 no problem or still buggy with some apps but fixed some others?
Click to expand...
Click to collapse
There are newer versions of xposed that fix compatibility issues with LG's encrypted apps (weather, etc) since my post, so they should work with the newer versions of xposed. I only recommended version v68 because I never really use LG apps so I went ahead with such an update. Hope this helps!
Xposed for visually impaired users
Hi, everyone!
I'm visually impaired and I've been "adapting" and customizing my stuff (for a better, more comfortable usability) since 1998 (for Win and Mac) and 2010 for mobile devices, with great success.
I could install the Xposed framework to my Galaxy Tab 3 running KK 4.4.2 (Serbian Stock) back in 2012. But I cannot find a way to install it to my LG L90 D410 running Lollipop 5.0.2.
The option for those specific brands and models in based on the need for good cost-benefit ratio pieces of equipment, so that anyone can benefit from my findings, even those running on a low budget.
I'm preparing a podcast and an YouTube channel on accessibility.
All that put, I'd appreciate any input on how to make the Xposed framework to work on the LG L90. Suggestions o modules that can be useful for vision impaired people will be very welcome too.
Thanks in advance for any help I can get.
For some reason my sprint note 4 all of a sudden stopped being able to install xposed framework through twrp. I'm running cm 12.1 rom and using the latest sdk but no matter what i do i still get .zip file is corrupt and twrp instantly reatarts. Can anyone shed some light on this for me?
friendofganja said:
For some reason my sprint note 4 all of a sudden stopped being able to install xposed framework through twrp. I'm running cm 12.1 rom and using the latest sdk but no matter what i do i still get .zip file is corrupt and twrp instantly reatarts. Can anyone shed some light on this for me?
Click to expand...
Click to collapse
Seems to be an issue with the .zip file. Download it again and check whether the problem still persists.
Yea i did. That's why i am a bit confused. I even tried an older version which i have installed countless times before after every nightly update but even that says corrupt zip now.
friendofganja said:
Yea i did. That's why i am a bit confused. I even tried an older version which i have installed countless times before after every nightly update but even that says corrupt zip now.
Click to expand...
Click to collapse
Did you flash a new nightly built of a custom ROM or a newer version of TWRP, maybe a bootstack? Such kind of things don't occur "all out of sudden".
I had flashed a new build of cm12.1. twrp is the same version. But i don't see what difference that would really make unless all nightlies since sept. 30th stopped support for xposed. Like i said before i had been reinstalling xposed each time i would update cm and never had an issue until recently.
No one has any ideas??
Go read the last few pages of the main thread. On Oct 5 they added a security fix to AOSP that broke xposed compatibility.
friendofganja said:
No one has any ideas??
Click to expand...
Click to collapse
A new version of Xposed (v75) is available. Download the correct version for your device and report back.
same issue
hello fellas i had same issue when i tried to install,
corrupt zip file.
i was using twrp 2.8.4
android 5.0.1
with sdk21 arm 32bits v80 (same of my phone)
we have in comom is that our phone carrier is the same, Sprint Glaxy s4 sph720
I also came across the issue with the xposed installer saying it's corrupt. Here is the entire process I went through and got around this:
(Device is LG G3 D855 running CM13)
1) Made certain all previous xposed apps were uninstalled (mostly the installer itself)
2) Also made certain any previous xposed framework was uninstalled
3) Booted back into TWRP and created a new backup (just in case)
4) Installed xposed-v83-sdk23-arm.zip via TWRP (did not reboot in between steps 3 and 4)
5) Rebooted back into system, takes a while since it optimizes all apps
6) Tried to install the XposedInstaller_3.0_alpha4.apk and ran into the corruption issue
7) Also tried XposedInstaller_3.0-alpha2.apk to see if it had the same issues (it did)
8) Installed de.robv.android.xposed.installer_v33_36570c.apk just to see if it would run, it did
9) Once de.robv.android.xposed.installer_v33_36570c.apk was installed I reran XposedInstaller_3.0_alpha4.apk and it installed successfully
10) Rebooted again
11) I was then able to download and install xposed modules
I went through all of this initially because I wanted the SU (#) indicator to be hidden. I had xposed installed on CM12 and it worked well for me. I have missed a lot of the features available with xposed.
I apologize if I have left out any pertinent info. If anyone needs more info, please reply here and let me know. If I see any questions, I will try to respond.
So I rooted and installed Xposed right when it was released for 6.0.1. Since my phone's been running fine since...I kind of forgot about everything and left it alone.
Now I want to uninstall/reinstall Xposed, but I seem to recall something about uninstalling causing a bootloop. I have the stock recovery right now (would FlashFire work though?) and I'm not sure if I need to flash, or will uninstalling from the Xposed app itself work fine? Could anybody help?
crazylilazn said:
So I rooted and installed Xposed right when it was released for 6.0.1. Since my phone's been running fine since...I kind of forgot about everything and left it alone.
Now I want to uninstall/reinstall Xposed, but I seem to recall something about uninstalling causing a bootloop. I have the stock recovery right now (would FlashFire work though?) and I'm not sure if I need to flash, or will uninstalling from the Xposed app itself work fine? Could anybody help?
Click to expand...
Click to collapse
The N6 is pretty bullet-proof as far as modding phones goes. I don't use Xposed, but I thought there was an uninstall zip:
xposed-uninstaller*.zip from http://dl-xda.xposed.info/framework/: Can be flashed with a custom recovery (e.g. TWRP) to uninstall the framework.
Click to expand...
Click to collapse
FlashFire was developed by Chainfire on an N6 (at least in part). I would take a fastboot backup using FF then if there is an option to uninstall within xposed, I'd go ahead and try it. If there is a problem, then use Fastboot to restore. This way, you can restore the FF backup without having to install TWRP on the phone.
I've personally done this several times while trying to make Snapchat work, nothing happened. For me, the bootloops where caused by a module and not Xposed itself.
Unless you're doing something funky like me, you'll be fine.
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry
larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
Thank you
Larry
Click to expand...
Click to collapse
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk
CyberZeus1977 said:
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk
Click to expand...
Click to collapse
Tell me somthing about "stock kernel" and "EX Kernel" what is that and how can i install that? or change that?
I have the same problem, galaxy S6.
I noticed losing root randomly and fixed it by going install patch boot img then you flash the boot img in recovery. So far it's been a day no root loss
Lineage 14.1 for lg stylo 2 plus
Hi ! I have sale problem with my S8+ with custom rom and Custom kernel
Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
I hope I will be able to get some more usefull information for you soon (LogCat etc etc.). If any one has an answer or suggested options it would be good. I am particularly interested in getting the Busy Box feature to work with Root as I am working on an app for my job that needs both options (I work offshore and am trying to adapt a piece of Seismic QC software (unix based) to run on phones / tab's - Android).
I will sign up properly and start to follow the threads more closely.
Cheers... Andy
-Samsung S6 - Full Magisk Module (with recommended zeroflte TWRP).
AndyQVT said:
Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
Click to expand...
Click to collapse
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry
Click to expand...
Click to collapse
See above
Thanks to all for the help
Nye-uhls said:
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
See above
Click to expand...
Click to collapse
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy
AndyQVT said:
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy
Click to expand...
Click to collapse
Glad everything is good! Sometimes magisk will get messed up, so just updating or even reinstalling will fix things.
Just keep in mind, its very likely you'll have problems again down the road... Samsung phones do a lot of weird stuff under the hood, and eventually symlinks will get broken, files deleted etc... So when that does happen, the best you can do is uninstall, reflash, update, and watch your modules.
Today updated to 15.3 and install James DSP root losed...When open magisk ask for installation reboot to recovery twrp install latest zip reboot open magisk it close it self and root lost again ?! Any advice from @topjohnwu
Do you guys mind posting a resource that shows how to root the S6 using magisk? I'm very rusty, last time I dealt with rooting was 8 years ago. Any help is appreciated. Thanks