Hi Guy,
I would really appreciate some help in resolving two issues I have on my Samsung Galaxy S2, yes I know its old, but it was given to me for FREE.
I have recently updated my phone to CyanogenMod 13.0-20161211-NIGHTLY and immediately, I realised that neither my Xposed Installer or SuperSU work. The update for the Xposed Framework v80-sdk23-arm.zip, that had previously worked on any CM NIGHTLY Updates, but once I use the same update, I am faced with a bootloop and therefore need to Restore from Backup. Whereas, SuperSU v2.46 has not worked for as long as I can remember, possibly all CM NIGHTLY Updates 13.
I have search the forum for the correct versions I require to get both these apps to work correctly and with getting a Bootloop once I have updated.
Please can anyone point me in the right direction.
Thanks in advance.
Try using V87. If it has the November 5th security patch it needs this version.
Also with cyanogenmod nightly it comes pre-rooted in the developer section so no need for Superuser
Cheers dude, for the advice.
I ended up wiping everything and restarting a fresh.
Related
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.
I'm sorry if this is in the wrong location, I'm quite new here.
I recently purchased a Tab S2 and decided I wanted to root it. I followed all the instructions listed in this thread, http://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627, and was able to successfully root it. I figured since that went so smoothly to try and install the Xposed framework for 6.0, and that's where the problem began. I'm not sure if I missed a critical step, but after booting to TWRP and installing the Xposed Framework I'm now stuck at the Samsung logo and unsure of what to do to get back on track. Any help would be greatly appreciated!
infinit_e said:
I'm sorry if this is in the wrong location, I'm quite new here.
I recently purchased a Tab S2 and decided I wanted to root it. I followed all the instructions listed in this thread, http://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627, and was able to successfully root it. I figured since that went so smoothly to try and install the Xposed framework for 6.0, and that's where the problem began. I'm not sure if I missed a critical step, but after booting to TWRP and installing the Xposed Framework I'm now stuck at the Samsung logo and unsure of what to do to get back on track. Any help would be greatly appreciated!
Click to expand...
Click to collapse
You installed the wrong Xposed. If you didn't make a backup with TWRP, TUT TUT!
You will need to reflash the stock firmware.
I admit I didn't make a backup, I was excited and got ahead of myself, but there's nothing on the device that I wasn't willing to lose. As for the Framework, I installed http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip which I got to from http://forum.xda-developers.com/showthread.php?t=3034811. I saw the notice on the Xposed site that points to that thread, so I thought I was doing the correct steps. Which framework version should I have used?
infinit_e said:
I admit I didn't make a backup, I was excited and got ahead of myself, but there's nothing on the device that I wasn't willing to lose. As for the Framework, I installed http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip which I got to from http://forum.xda-developers.com/showthread.php?t=3034811. I saw the notice on the Xposed site that points to that thread, so I thought I was doing the correct steps. Which framework version should I have used?
Click to expand...
Click to collapse
you should flash modified xposed for samsung device [Link]
Thank you! I'll give that shot!
All set now, thank you!
Hey everyone.
I can't install the Xposed framework. The error messages are in the the screenshots you'll see attached.
(EDIT: I can't post outside links since i am a new user, also i am by this Time unable to upload screenshots.. i'm working on it.)
de(DOT)tinypic(DOT)com/r/2cx89yd/9
de(DOT)tinypic(DOT)com/r/14ufkvo/9
I am currently using an OnePlus 3 with oxygenOS 3.26 flashed via twrp.
Before I was using 3.24 where everything was working fine. Then I switched to sultanxda's CyanogenMod. Since the Home Button was not working correctly, I decided to go back to the just released Oxygen. Everytime I was clean installing it.
From there on I am unable to use Xposed. I flashed it many times, used different twrp versions and also the arm64 v85 instead of v86. Nothing really wants to work.
I thought, i am may not able to flash anything because the System is set to Read-Only, but flashing SuperUser.zip has worked without any problems.
I'll appreciate your help.
P0ttiBoo said:
Hey everyone.
I can't install the Xposed framework. The error messages are in the the screenshots you'll see attached.
(EDIT: I can't post outside links since i am a new user, also i am by this Time unable to upload screenshots.. i'm working on it.)
de(DOT)tinypic(DOT)com/r/2cx89yd/9
de(DOT)tinypic(DOT)com/r/14ufkvo/9
I am currently using an OnePlus 3 with oxygenOS 3.26 flashed via twrp.
Before I was using 3.24 where everything was working fine. Then I switched to sultanxda's CyanogenMod. Since the Home Button was not working correctly, I decided to go back to the just released Oxygen. Everytime I was clean installing it.
From there on I am unable to use Xposed. I flashed it many times, used different twrp versions and also the arm64 v85 instead of v86. Nothing really wants to work.
I thought, i am may not able to flash anything because the System is set to Read-Only, but flashing SuperUser.zip has worked without any problems.
I'll appreciate your help.
Click to expand...
Click to collapse
Please use the corresponding Xposed thread or OP3 forum for your issue.
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
Hi all when flashing any version above v12 on to my phone it gets stuck at the boot logo I am using Lineageos latest version of typing this but if I use v12 its fine but dont pass the CTS and stuff
I have tried to fully uninstall the magisk and reinstall it on the newer version and nothing can anyone help please
I have also fully reinstalled the ROM with formatting everything and it still don't boot
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
ldeveraux said:
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
Click to expand...
Click to collapse
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on the first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Jet45 said:
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on thé first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Click to expand...
Click to collapse
So glad someone eles has the same problem and I'm not on my own it just seems weird how the v12 works it don't pass but all loads fine. Let hope they find why and fix it.
Flash your stock bootloader then try flashing magisk
I'm using the stock bootload not changed my bootloader
If it was the bootloader why foes v12 work fine?
No request to have any information about this ?
What do the devs need (other than time of course) to try a troubleshooting ?
How to get this logs/boot image and logs ?
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Recycool said:
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Click to expand...
Click to collapse
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Recycool said:
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Click to expand...
Click to collapse
So I'll try to reproduce it at my side with that you've said, it may be a walktrough . Two brains to work on it may succeed
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I posted a logging of the problem on the main support thread, let's see what happens
https://forum.xda-developers.com/ap...sal-systemless-t3432382/page1765#post73249492
cross the fingers (I hope that you say like that in English)
Fingers crossed they sort it. Would love yo be able to use magisk again
Does anyone here have this issue on a stock ROM or is it just Lineage OS? From the log that was posted in the main support thread it looks like the Magisk installation was successful, but the system hangs on this one line before it can fully boot. I'm not qualified to read more than that out of the log though...
There's been some code added to GitHub in the last few days. Have anyone tried the latest unofficial snapshot? There was a new one built yesterday: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Hi we got anymore news on this I have tried the latest beta one and it still gets stuck at booting.
It seems there is nothing to expect from nor magisk team neither lineage team. Nobody seem want to work on this really specific problem.