yashsingh1/xdaforums huggingface dataset:
[Xposed General] Ibuprophen:
Please refer to this post and you'll see the great effort being made to remedy the issue. If there are no commits... It doesn't mean that it isn't being worked on.

Everyone will have to be patient :cool: .

Peace and Love!

Peace and Love!
[Xposed General] rambomhtri:
Hi, I've just installed Xposed 3.1.1. In the "Xposed Installer" tab, I'm getting a warning saying "Could not load available ZIP files. Pull down to try again.". I don't have any zip files in the memory, and pulling down doesn't remove it.

What does that warning means?

I think it should not appear there if everything was fine.

Edit:

I reply myself, I think it was because I didn't have Internet connection so the list of the versions couldn't load. Nevertheless, the warning should be "the list couldn't load" or "there's no internet connection". I still don't know what that warning meant.
[Xposed General] Didgeridoohan:
The november security patch broke Xposed. There is no Xposed for Nougat...
[Xposed General] sdeft:
which post do you mean ?
[Xposed General] fKm:
https://github.com/arter97/android_frameworks_base/commit/35724b039e7a990950100354d01467c05756de37

That commit works for me. Running CM with latest November security update and Xposed with all my modules enable.d
[Xposed General] mahe.:
deleted.
[Xposed General] IMTLD:
Can I edit the respective file without using android kitchen?
[Xposed General] fKm:
What do you mean with Android Kitchen? You have to compile the whole ROM to use that commit. It is not possible in any other way.
[Xposed General] IMTLD:
I thought editing the file would be easy, but it seems very complex-for a noob:p. Seems I gotta wait for more time till xposed releases new version
[Xposed General] bdwilk:
What ROM are you using?
[Xposed General] LuciferIII:
Uups sry meant M
[Xposed General] IMTLD:
cm13 mi5
[Xposed General] bdwilk:
I just wanted to say if its not a stock ROM then you'll have to decide which is more important to you. For me, having Xposed is better than being on the latest nightly. Just saying.
[Xposed General] friscoboi:
Xposed sdk 23 v 86 does not work with cm 13 for i 9515 with newest kernel 3.4.113 anymore. Hope there will still be updates for xposed sdk 23????

Quote:

Originally Posted by friscoboi [MENTION=5010221]sombree[/MENTION] 20161115 got me stuck in a bootloop so far. I did everything as always with updates? Or does it take more than 30 minutes to reboot with the new kernel the first time?

It's because you're using xposed. And no, I'm not going to rebuild ROM with one of those unofficial fixes - you'll have to wait for fixed xposed

(Just saw the issue has already been adressed. So, I will wait for sdk23 v87:)
[Xposed General] image45:
cm-13.0-20161112-NIGHTLY-kipper.zip

Updated to above version, however when I tried to install xposed-v86-sdk23-arm64.zip, after phone gets stuck on bootloop!

Anyone had same issue at all please?
[Xposed General] wurstherpes:
I have the same problem!
[Xposed General] image45:
Well that's good and its bad as I am not alone then!

Issue seems to have started since the Android security patch level; 5th November 2016 was added to ROM!
[Xposed General] ml48603:
Enabling any module results in an incomplete boot.

Installed the X-Posed Framework xposed-v86-sdk23-arm.zip from TWRP 3.0.2.0 on a CM13.0 Marshmallow 6.0.1 nightly build released 11-14-2016

Installed the Xposed Installer apk 3.11 from within the running CM13 system and rebooted without a problem.

Smartphone is Samsung S4 SGH-i337

After loading and enabling a popular module that has been modified to work on CM13, BootManager then rebooting CM13 will not complete loading. Waited 10 minutes with the Blue CM Droid icon flashing just to see if Android would eventually load.

To get the phone to boot normally again, TWRP recovery is entered and and the following files is deleted with the file manager: /data/data/de.robv.android.xposed.installer/conf/modules.list

Xposed keeps track of all enabled modules in this file. With modules.list deleted, all modules are disabled upon reboot

If I don't enable the module in the Xposed Installer app, the phone boots up normally. I tried installing another well known module and enabling it only, leaving BootManager disabled. Upon reboot I see the same behavior, ie. Android never completes booting. This occurs with any given CM13 module I load and enable.

I am not seeing boot looping, where the phone shuts down and turns back on at infinitum, but rather a boot and the OS never completes booting and the Cyanogen robot icon flashes.

What would cause the Xposed Framework and installer to not let the system boot normally? How can this problem be resolved?

Thanks in advance, Mark
[Xposed General] DKnightX91:
The November 5th 2016 security patch is causing the problem. Either remove Xposed right now or go back to a rom without the patch. I believe they're working on a patch right now for Xposed but no idea when it will come out.

You are right.
[Xposed General] ml48603:
Thanks DKnightX91

I will wait for the Xposed patch then and discontinue the troubleshooting. Will the patch be applied to the zip installed from recovery or will the patch be only applied to the Xposed Installer apk ?

Is there somewhere where a notice of the Xposed patch release will be posted?

Do you know if that android security patch was targeted specifically at disabling Xposed usage in the future ?

Looks like the CM13 build just before 11-5 was cm-13.0-20161102-NIGHTLY-jflteatt.zip (340.94 MB)

I could try loading that and leaving the apps i have installed alone to see if the apps would still work.
[Xposed General] piskor:
[MENTION=6206893]ml48603[/MENTION]

Please read this http://xdaforums.com/xposed/discussion-xposed-marshmallow-t3249095/post69622412#post69622412
[Xposed General] ml48603:
Thanks piskor, That settles it. Got a little too "bleeding edge" for my own good. I'm loading up the 11-02 version right now to test Xposed with the pre-11-05 security patch.

Looks like the apps won't have to be reconfigured, rolling back from the 11-14 nightly to the 11-02 nightly.
[Xposed General] image45:
Yes it looks like we are all stuck on the 11-02 nightly if wanting to remain with fully functional exposed enabled devices.
[Xposed General] AndyYan:
Or if you/your maintainer builds one that patches it on the ROM side - we've discussed this on prior pages. I'm running a patched personal build on my N6P just fine.

Sent from Google Nexus 6P @ CM13
[Xposed General] prax31:
Need to keep mobile data on for an app while rest use WiFi??

Hi all,

Pls suggest me any xposed module that can keep mobile data always on for an app while the rest of apps use connected wifi . This is useful for people in India who dont have a VoLTE device and are using Jio4gVoice app to make calls and texts.

If any developer can make this possible, Indian users will appreciate your work
[Xposed General] friscoboi:
There is no Solution. Go back to the older Rom to use xposed. Or use the newer Rom and use NO xposed.
[Xposed General] Katzenmuetze:
Quick question:

I'm using MM 6.0.1. with AndroPlus Kernel v40, Security Patch Level August on a Sony Xperia Z5 Compact.

Can I use Xposed or will my phone go into bootloop? And which version do I need (x85, arm, arm64)?
[Xposed General] bdwilk:
SDK23 arm64

It should work, but always best to do a nandroid backup and try it out. Worst case then would be to restore your backup.
[Xposed General] friscoboi:
If you get in a bootloop: just Flash the Rom again without xposed. Should get you back.
[Xposed General] bdwilk:
You're telling the wrong person. I'm not the one asking for help.
[Xposed General] cva_kabil:
No need of xposed module,Use macrodroid Automation app..
[Xposed General] otyg:
Was this security patch assumably from google targeted to break xposed or some other serious secuity hole that just happened to break xposed , Also has there been any progress bypassing it from xposed level? or is it looking pretty dim without android source modifications, no hurry, i'm just curious :).
[Xposed General] Phrodini:
Some users and devs have implemented a framework fix to their rom that allows xposed to work with November patch

Rovo said he's aware of the problem
[Xposed General] zelendel:
It just fixed a security hole that Xposed uses. You have to understand that to many (google encluded) Xposed is a huge security issue. So it is only a matter of time before google plugs all the holes that xposed uses. At that point you will have to use a rom that is built to work with xposed. To be honest there will be few that will make changes just to work with xposed. Most advise not to use it on custom roms.
[Xposed General] friscoboi:
So, probably xposed is dead now. Loved cm 13 with xposed. Especially greenify with xposed Options...
[Xposed General] Portgas D. Ace:
Why don't you stay on CM13 with security patch level of October? Having Xposed installed makes security patches more or less useless at all.
[Xposed General] friscoboi:
But I want the test of the Updates, New Kernels...

Giving cm a try without xposed now:)
[Xposed General] fedosis:
U can build cm13.1 on your own PC with little patch and xposed works great again.
[Xposed General] zelendel:
Xposed will have a place on stock based roms as it was intended. So not dead but will most likely be less used.

People will have to get used to having less options with things like this and root. With the way OEM and Google are locking android down, the time will come when you ha e to chose between custom stuff Or having the latest flagship.
[Xposed General] friscoboi:
So I take the newest cm 13 and modufy it? Have a Link that tells me how to Start?

---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------

So, this is how I get the newest cm 13 to work with xposed again??? How do I get that Code in there?
[Xposed General] LBSpeller:
But only on old stock based roms, as anyone who has relieved an OTA with the November security patch will no longer be able to use xposed. Over time this will affect more and more users, regardless of if they use custom ROMs or stock.
[Xposed General] fedosis:
This explains how to build CM from source

https://wiki.cyanogenmod.org/w/Build_Guides#vendor=;

And this - changes in code U need to allow Xposed to start

https://github.com/arter97/android_frameworks_base/commit/35724b039e7a990950100354d01467c05756de37
[Xposed General] jeepcook:
New commit from cm sources:

zygote: Allow device to append extra whitelisted paths

Is this we are waiting for??

Envoyé depuis Tapatalk
[Xposed General] otyg:
I doubt that since security patches come from google so any stock rom ota update will likely include the latest security patch, I am waitimg for the next miui update to see if this is true if it is then the only option would be to switch to patched cm builds.
[Xposed General] Nergal di Cuthah:
I have to agree with others on this. Stock AOSP and OEM, and likely SDK24 in total, will be like this. The patch isn't a CM issue, it's a Google patch. Rovo's hard at work fixing, but it'll be some amount of time to conquer
[Xposed General] Ibuprophen:
Please Read This Post:

[ANNOUNCEMENT] CM Bootloop Issues and XPosed with Early November CM Releases...

It Explains It All...

Just Be Patient...

"Patience is a virtue..."

Peace and Love!

Peace and Love!
[Xposed General] Ferrumlan:
Is CM trying to fix problem?
[Xposed General] LuciferIII:
Pls someone answer ,anyone?
[Xposed General] swat4samp:
Sorry for OT, anyone using that xposed fix in their ROM, can you check whether location is working fine?
[Xposed General] mahe.:
we probably test our-self and see. I will test my self(with the backup) this weekend and see it getting fix or not :)
[Xposed General] pax2011:
CM will not fix it
[Xposed General] LuciferIII:
:crying:
[Xposed General] pax2011:
We have to wait for new xposed version
[Xposed General] awakener777:
Actually, yes this fixed it. I can confirm. CM fixed it with this commit. Xposed now works on CM.

CM fixed with latest commit
[Xposed General] LuciferIII:
Soo,why do people say they fixed it
[Xposed General] pax2011:
I was wrong
[Xposed General] LuciferIII:
Guys i tried to install the latest build but still bootloop with xposed
[Xposed General] Phrodini:
Some people added a framework commit to their ROM that fixed the issue..ex..unofficial resurrection 5.7.4 ROM
[Xposed General] LuciferIII:
Is cm gona do it?
[Xposed General] Phrodini:
I Don't have information on that
[Xposed General] awakener777:
I rescind this statement. Though it doesn't boot loop, and I'm able to enable modules, and the xposed app says framework is active, the modules do not seem to be having any effect [emoji22]
[Xposed General] Ibuprophen:
Everyone, please read this post...

[ANNOUNCEMENT] CM Bootloop Issues and XPosed with Early November CM Releases...
[Xposed General] friscoboi:
So, I just have to wait for my next Update and it works? Or do I have to whitelist a path somewhere?
[Xposed General] Nishblueweapon:
Has anybody made workaround for oos3, November build?
[Xposed General] fedosis:
New commit to cm-13.0 allow developers to permit installing and work xposed on their builds, but it works only at build phase.

U can create overlay for device repo like this

https://github.com/fedosis/w5_xpose...frameworks/base/core/jni/fd_utils-inl-extra.h
[Xposed General] QayyuMirul:
Hello. Anyone can tell me which xposed should i use? My phone samsung j7 sm-j700f
[Xposed General] friscoboi:
What Android Version is on there?
[Xposed General] QayyuMirul:
Marshmallow 6.0.1
[Xposed General] Portgas D. Ace:
Stock ROM or custom ROM? If custom ROM: is it based on TouchWiz?
[Xposed General] Ibuprophen:
Okay, i think everyone is over analyzing the issue...

@rovo89 (and his crack team of experts) is, in fact, currently working on the XPosed Installer/Framework regarding the bootlooping issue when the XPosed Installer is installed and a module is active within the installer.

I just posted the thread (below) that explains the problem.

I inquired about the issue with a Cyanogen dev and passed the response via the information within the post (above).

The Cyanogen dev(s) are not actively against XPosed, they just don't/won't support it because it is a third party modification (which i understand completely). They have no intentions to rework the security updates to allow XPosed to work again and stated (as polite as they can be) that the XPosed Dev(s) will need to adjust/modify XPosed to work on CM again with the security updates they implemented.

They didn't actively update CM ROM's to stop/prevent XPosed from working. XPosed just happened to be affected inadvertently without any intention in doing so.

The early November CM Nightly's, Snapshots, etc... Have the security updates. In my case, those security updates were implemented for the D2VZW CM13 Nightly beginning with the 11 November Release. So i am forced to continue to use the 08 November release since that is the last release that XPosed will work on.

Finally, when @rovo89 and his team (who are working really hard) figure out a fix/modification to XPosed, it will be announced. Remember that Patience is a Virtue!

~Ibuprophen
[Xposed General] QayyuMirul:
Custom ROM. Stock Optimized v3
[Xposed General] grep_i:
Old news there were workarounds before Rovo89 knew about this problem. The ones who cannot wait that long are already using them one of them you're using others revert a certain commit and some change a file on the device, rovo89 said it won't be a quick fix.
[Xposed General] bdwilk:
It's still based on TW so you need to search for Wanam Samsung Xposed
[Xposed General] AndyYan:
All okay on my side - running a personal build on my own N6P.

Sent from Google Nexus 6P @ CM13
[Xposed General] QayyuMirul:
Okay. Thank you very much
[Xposed General] TheHaso:
Still bootloops on latest nightly 1119 with the zygote commit.
[Xposed General] ethanscooter:
What are the workarounds?
[Xposed General] Hanabishi Recca:
Temporary solution for latest security patch in Android 6.0.1 MM

*** Deleted, use official test builds ***

(if you installed this before)

Modified uninstaller: View attachment xposed-uninstaller-WB.zip
[Xposed General] eliaslear:
Is this for 64 only or can it ba flashed on arm?
[Xposed General] Codebucket:
Yes, this is only for arm64 :o
[Xposed General] Hanabishi Recca:
Only for ARM64. ARM(32) version will be a bit later.
[Xposed General] eliaslear:
Aw. That sucks. I'm still rocking my nexus 6. I can't seem to move past the screen. Lol. I might try it on my pure or 6p tonight.
[Xposed General] Hanabishi Recca:
ARM version is now avaliable ;)
[Xposed General] eliaslear:
OMG! where? Please post link! Thank you.

Never mind i see it. Thanks so much!
[Xposed General] Hanabishi Recca:
Edited the post http://xdaforums.com/showpost.php?p=69699345&postcount=4504
[Xposed General] mooms:
Thank you, it works :good:
[Xposed General] grep_i:
Is it hard to read, the workarounds are even mentioned in the same post you quote.

Saw another workaround one post below yours this one I did not mention in previous post.

another workaround that's working with november patch
[Xposed General] eliaslear:
It works great! Everything i was missing. Thanks
[Xposed General] manankatwala:
Not working

I tried it on my OPX running OOS 3.1.4 and it sends into bootloop. Any chance of getting an uninstaller? :crying:
[Xposed General] manuelmagix:
I think, no fixed, cm13 security pacht 11/05 no bug, problem is with security patch 11/01.

worked fine cm13 for bq X5+, with security pacht 11/05, but cm13 with security patch 11/01 +"tempory soluction" dont work.
[Xposed General] eliaslear:
Works great on nexus 6 on resurrection remix 6.0.1 with newest November patch that broke old xposed.
[Xposed General] comediiian:
Tried to install the new .zip and i got the same error ?

Not enough space on disk .. what did i wrong?

Runnin a OP3 with latest Beta7, modified twrp 3.0.21
[Xposed General] Hanabishi Recca:
Try to disable "Zip signature verification" in twrp settings.

---------- Post added at 00:24 ---------- Previous post was at 00:23 ----------

Use standard xposed uninstaller.
[Xposed General] ibchh:
Bootloop on BQ X5+ with latest stock. Uninstaller didn't work for me.
[Xposed General] comediiian:
Its already disabled, still dunno work.

Everytime the same error like before, not enough space on disc ..

Anyone else who tried this "workaround" on OP3 with Beta7 ?
[Xposed General] Hanabishi Recca:
Yeah, just checked, standard uninstaller didn't work.

Added modified uninstaller to the post.
[Xposed General] comediiian:
Ok .. System Partition is full .. dunno why .. install work now, but ends with bootloop after xposed install ..

Dont work on my OP3 with Beta7.
[Xposed General] MrMoi:
fix available here => http://dl-xda.xposed.info/framework/sdk23/arm/xposed-v87-sdk23-arm-test1.zip for the nov security patch issue
[Xposed General] comediiian:
Arm32?

Whats the difference between this and the other, postet a few hours before (arm64 whitelist) ?
[Xposed General] MrMoi:
arm 32 => http://dl-xda.xposed.info/framework/sdk23/arm/xposed-v87-sdk23-arm-test1.zip

arm 64 => http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v87-sdk23-arm64-test1.zip

these fixes are official by rovo89
[Xposed General] comediiian:
Thank you man .. ill give it a try :)
[Xposed General] konfuzius4u:
works fine in HTC One M7 with latest CM13
[Xposed General] Phrodini:
Good stuff
[Xposed General] jeepcook:
Great job, works fine! Thanks

Envoyé depuis Tapatalk
[Xposed General] raphael.e:
Works fine for Nexus 5 with latest CM13 and elementalx kernel
[Xposed General] Schnedi:
Working perfectly on Xiaomi Mi5 with CM13 ?
[Xposed General] CRXed:
For anybody trying the "test1" builds that Rovo made, be aware that there are probably memory leaks still in his code.

// TODO Could there be any memory leaks because of this?

Let's wait for test2 a bit.
[Xposed General] sandpox:
deleted
[Xposed General] ipdev:
Seems to be working on my Nexus7 2013 (flo/razor)

bootloader-flo-flo-04.08.img

image-razor-mob30x.zip

twrp-3.0.2-0-flo.img

cm-13.0-20161112-NIGHTLY-flo.zip

open_gapps-arm-6.0-pico-20161117.zip

xposed-v87-sdk23-arm-test1.zip

XposedInstaller_by_dvdandroid_19_11_16-release.apk

- GravityBox[MM]v6.2.1
[Xposed General] bipindr123:
Great job guys, it works on rr 6.0.1 November security patch arm64
[Xposed General] friscoboi:
What are memory leaks?
[Xposed General] moffa~:
When unused memory is not released so the program's memory usage increases indefinitely and you run out of ram on your device.

The workaround is rebooting.
[Xposed General] Ibuprophen:
I performed a fresh install with the updated CM13 (that has the AOSP Security Patch) and installed your ARM XPosed Framework zip and it still got stuck in the CM Bootup Splash Screen.

I believe that this is specific to certain device that has the AOSP Security Patch included.

It was a great job you did but, it will work for some and not for other's.

Not your fault, just the way the Patch was implemented within the devices.

GREAT JOB!!!
[Xposed General] fedosis:
There is official xposed-87-test1 from rovo89.
[Xposed General] Hitti2:
Where is download link for latest xposed?

---------- Post added at 05:09 PM ---------- Previous post was at 05:06 PM ----------

Found it buried.

http://dl-xda.xposed.info/framework/sdk23/arm64/
[Xposed General] J_E_F_F:
can the test zip be installed OVER v86, or does that need to be removed before installing the v87 test zip?
[Xposed General] Ibuprophen:
Yes it can.
[Xposed General] phatrick:
Is there a x86 version yet?
[Xposed General] nabeelrazanaqvi:
Hi guys. I have strong problem please help me

I ha e E6633. Flashed existenz marshmallow Rom. When I flash arm 64 based Xposed it says wrong zip. When I flash any other Xposed version 86.6 it can not be activated in Xposed installer apk. What I am doing wrong. Please help me

I have tried Magisk method as well but no success

Thanks in advance
[Xposed General] GasLoop:
Check "About Phone", if "Android Security patch" reads "November", Xposed won't work.
[Xposed General] rambomhtri:
I had a screen filter activated when I tried to install the latest YouTube AdAway through Xposed Installer 3.1.1 (Material Design). I downloaded it successfully, but when I tried to install it, the "Install" option wasn't working. I touched "Cancel", and tried it with the previous last version, the same happened.

Then, I realized it was because of the screen filter. I deactivated it, and installed the latest version successfully. Nevertheless, now I have downloaded and "ready to install" both versions, because the "install" button has not disappeared, as it's supposed to do. You can see that in the attached picture.

What do I need to do to remove the downloaded and not installed versions? (It's weird because I have the latest version installed but still have the option to install it)
[Xposed General] Hanabishi Recca:
Go to your system settings > storage and clear the cache.
[Xposed General] veedz:
thank this works fine on redmi note 3 with latest resurrction remix and radon kernel
[Xposed General] rambomhtri:
You sir, deserve a good day and a nice glass of wine! :cowboy:

:highfive:
[Xposed General] ml48603:
fedosis, Thanks for the How To Build our own links. I am interested in that but didnt know where to start researching it to learn.
[Xposed General] JimTimmler:
xposed works again, thanks!

Tested today latest cm13 nightly (cm-13.0-20161117-NIGHTLY-i9300) for my Samsung galaxy S3 with xposed-v87-sdk23-arm-test1 build.

Works perfectly with my modules so far. No bootloops, no reboots and the modules do what they are supposed to do.

Thank you very much for this fast fix! It works.
[Xposed General] rloup:
Just installed the new test1 version. All works fine on my bq aquaris x5 plus. Thanks!
[Xposed General] Ibuprophen:
The E6633 has an Quad-Core ARM Cortex Processor.

You need to use the ARM Not the ARM64.

Reference:

http://www.phonemore.com/compare/ph...al-e6683-vs-sony-xperia-z5-dual-e6633/2809636
[Xposed General] Brulsturm:
What are my options? patch level is indeed November 2016.