yashsingh1/xdaforums huggingface dataset:
[Xposed General] deathscythemeng:
Yes, it is brought by merging AOSP 6.0.1 r74 on Nov 10. It adds a security check in app_process that it only allow files in a const whitelist and jars in framework folder running. And xposed try to run some user apps in /data/app/, and it is not allowed, so system is stuck there.

I just disable the whitelist check in my own build, and it seems to work.
[Xposed General] Alexey71:
Can detail how to disable?
[Xposed General] zg85:
Maybe this could help https://github.com/HealthyMarshmall...mit/42c6677914a37933fbe8da5a74d0488ea8d035c5?
[Xposed General] Kucher90:
Htc one m8 eye "xposed"

Hi guys,

I just rooted my HTC One m8 eye

running marshmallow 6.0.1

So is there xposed for my phone .
[Xposed General] bdwilk:
Use sdk23 arm
[Xposed General] deathscythemeng:
I find that if an enabled module is updated, xposed and the module itself and some other related app will be forced closed. After rebooting, although it shows the module is enable in xposed app, it is not enabled indeed. After disable it and re-enable the module and another reboot, the module will work normally. So I think the workaround is not enough and still buggy. I have no time catch a log and read through it, as I have a biz trip tomorrow. Looking forward to someone's help on analysing.
[Xposed General] pico hackr:
when i try opening freecharge app it throws an error saying this app has been hooked to an third party app and it gets minimized itself . if i disable xposed my device never throw such error
[Xposed General] Schnedi:
Same here on Xiaomi Mi5 with CM13 Nightly from Nov 12.
[Xposed General] obongo:
Same, November 12 nightly
[Xposed General] bbernardini:
Ah, same with me on a Nexus 7 2013 with the November 12 nightly. I thought it was just me.
[Xposed General] gregfrankenstein:
This is especially problematic because the November 12th nightly for CM 13 is the first with the November security patch, at least for my Nexus 5. Unfortunately, I had to choose security over mods.
[Xposed General] marzametal:
Could not load available zip files. Pull down to try again.

I have provided a screenshot of my Xposed screen. It says the following message: (I have gone through pg 1 - 194 & pg 399 - 436 of this thread, will read on...)

"Could not load available zip files. Pull down to try again"

I have checked /data/data/de/robv.android.xposed.installer/conf

1) enabled_modules.list contains AFWall and XPrivacy

2) modules.list contains base.apk files for both AFWall and XPrivacy

I have checked /data/data/de.robv.android.xposed.installer/log/error.log and all entries seem fine; nothing inside that indicates a break, warning, error, not found etc...

I am also able to tick the checkboxes in the Modules section for the above two apps.

In AFWall / Preferences / Languages & Plugins, I am able to tick the checkbox related to leaky "Download Manager" Xposed fix.

I am using the CM 13 in-built Privacy Guard, since I read somewhere on this forum that SuperSU doesn't work with CM13? (or maybe CM13 on S2...)

Does this mean I can ignore the warning message? In my reading so far, I have noticed that some modules haven't been updated for Marshmellow. I was wondering if this warning relates to those modules (or even the zip file itself), or to the two modules I am using. Thanks in advance for any feedback.

Phone: Samsung Galaxy S2 GT-i9100

ROM: cm-13.0-20161105-NIGHTLY-i9100

Android Version: 6.0.1

Kernel: kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100-for-ODIN (used this kernel so I could repartition with a PIT file... I wanted to install GApps and extract the .so file related to swipe, then clean install without re-installing GApps and just copy the .so file over) ... I think the TWRP version is 3.0.2.x

Xposed - 3.1.1 v86

Xprivacy - 3.6.19 (481)

EDIT: can't read any more pages... gonna' take a nap while listening to Metallica.
[Xposed General] IMTLD:
Mi5

Clean install, latest cm13 with gapps and supersu only.

once I enable any module the phone enters bootloop
[Xposed General] swat4samp:
Are you sure it's Xposed? I too face this and in my case, it's due to AdAway blocking google ads.
[Xposed General] DKnightX91:
The new CM13 nightly 11/12 breaks Xposed. Is there a fix?
[Xposed General] Portgas D. Ace:
Read the last three pages of this thread.

From my understanding it simply indicates that Xposed Installer does not have access to the internet and thus can't download the list of available zip files for different framework versions. Did you restrict internet access for Xposed Installer via XPrivacy or AFWall+?
[Xposed General] marzametal:
Holy crap!

Yes, I did restrict it. I think I only enabled internet access for Xposed once, when I updated the modules list.

I just tested your theory, and hooray, warning gone! You are a legend, thanks so much!

I think I will keep reading the remaining hundred or so pages; I have found some interesting info in posts that will come in handy when starting from scratch, or when updating releases etc...
[Xposed General] CRXed:
Not just nightlies, every ROM, official or unofficial, that includes the November security patch is no longer able to boot with Xposed.

No fix unless you build your own ROM(see previous posts)
[Xposed General] pico hackr:
yes i am sure buddy , i never use any adblock , host files in my device are stock only i never modified it
[Xposed General] DKnightX91:
Thanks for the info. I'll just go back to an older update. Building a custom ROM is to advance for my skills as of now.
[Xposed General] Ibuprophen:
I tried out the latest CM13 Nightly for the D2VZW dated 12 November and i found that there is an issue after installing the Xposed Installer. Framework installs just fine but, after wiping and installing the previous CM13 Nightly dated 08 November, all worked great.

I'm not sure what had happened but, I'll wait for the next release of Nightly in hopes of it working with the Xposed Installer.
[Xposed General] Fif_:
The November Android security patch prevents Xposed from loading, and CM merged that code recently.

I'm sure the CM folks will whitelist XposedBridge.jar and everything will work again.
[Xposed General] invisiblek:
I can 100% guarantee this will not happen. CM will definitely not whitelist this due to security reasons.

EDIT: To build on that, CM not shipping a patch whitelisting xposed is no different than an OEM releasing a build with these patches in it (which they inevitably will). This will need to be fixed in xposed's installation anyway in order for this development to continue. Pretty sure you could ship a custom libandroid_runtime.so in order to achieve this...
[Xposed General] deathscythemeng:
I think it is not related with xposed itself. The rom needs to put all 3rd modules into the whitelist, and it is not possible. So we need to find methods of tricks in xposed, not the rom side.
[Xposed General] marconiglio:
Latest CM13 november 13th.

Only Boot animation on OnePlus One.

It boots only without flashing Xposed v86.

(Rooted and with Latest installer)
[Xposed General] rogers11:
And you think that this is something new?
[Xposed General] Kucher90:
Htc one m8 eye 6.0.1

Thanks for replying,but does I have to install a custom rom. And can you please send me the link of the proper sdk 23 arm and xposed installer and firmware for my phone which is HTC One m8 eye 6.0.1 , because I can't find it anywhere. And I would really appreciate it. Thanks for your time .
[Xposed General] Portgas D. Ace:
Those information can be found by searching XDA. Xposed is a powerful mod, and without knowing what you are doing, there might be a high chance of a brick. But from above statement, you already figured out which version to install, so read the first post of this thread, which contains all required information.

And you don't need a custom ROM to install Xposed.
[Xposed General] swat4samp:
You are right. I disabled adaway and freecharge still didn't work. It must be due to xposed. Not sure how to report this bug though :(
[Xposed General] Kucher90:
Thank you

Thank you.
[Xposed General] chitown835:
When I tried it on my phone it was a success but after activating The module and rebooting it bootlooped
[Xposed General] marzametal:
Damn, you bet me to it... hehe

I came back on to say the same thing, the Jenkins version allows for Xposed installation, but as soon as I added XPrivacy, and followed the necessary steps to get it working, it produced a bootloop.

Phone: Samsung Galaxy S2 GT-i9100

ROM: Jenkins release - cm-13.0-20161114-NIGHTLY-i9100 (November Security Patch included)

Android Version: 6.0.1

Kernel: kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100-for-ODIN...I think the TWRP version is 3.0.2.x

Xposed - 3.1.1 v86

Xprivacy - 3.6.19 (481)
[Xposed General] muhrizky:
Xposed v86 is compatible, meanwhile module is not working and creating bootloop?

Will/do Greenify and GravityBox works?
[Xposed General] AndyYan:
It does look like any module installed by user will be hitting the whitelist problem and bootloop. I clean flashed just for experiment, and it boots right up (cuz no modules are enabled yet), but subsequently enabling anything (used Greenify as example) will drop you into that cursed loop.

Anyone knows which patch exactly broke this, and whether it's revertible without side effects? Since I already build CM for my own devices, if possible I'd just revert it.

Anyways, returning to October's build for now. I need PerfectColorBar and Greenify badly...
[Xposed General] mobiupdates:
please also suggest me on this
[Xposed General] marconiglio:
No. I Think you are quite unpolite...

Especially if I was writing a post and when I finished there were 4 more new posts, treating that thing

Hey kid... Keep calm.

I'm 50 and sure I don't let you silly kid trolling me.
[Xposed General] rogers11:
Sure. The post before yours is 49 minutes older. You should try to write a little bit faster. :)

BTW: The silly kid is older than you.
[Xposed General] FlemishDroid:
It has nothing to do with no space because when Xposed framework is active and I try to download an module I get the "out of space" message but when Xposed framework is not active I can download modules from Xposed apk. If it was really out of space I got the "out of space" message also when Xposed framework is not active think.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Xposed General] Enddo:
With version 78 out now, is it okay to dirty flash the new zip over my installation of version 77?
[Xposed General] motoridersd:
I disabled the Greenify module and the random reboots on my 6P have stopped. I still have Unwatch running, so I think I found the culprit. Hopefully the devs will figure this one out soon, but for now Naptime seems to be doing a pretty good job.
[Xposed General] yukkio:
Yep, greenify causes random reboots here too. Disabled and no mute reboots... I think it's related with the incoming notifications.
[Xposed General] shakuyi:
For everyone on Greenify disable GCM push and the random reboots will stop
[Xposed General] motoridersd:
Good to know. I'll leave it off until this is fixed since GCM push is the only reason I use Greenify in the first place.
[Xposed General] geoff5093:
Really? I never Greenify apps I want notifications for, I always use it to minimize the impact of apps I don't need running int he background. I've tried GCM push before but it was always hit or miss if notifications came through.
[Xposed General] motoridersd:
Most of the apps that keep my device awake are ones I'm interested in getting notified about. It works very well. I usually do this with apps like Instagram, Facebook, Facebook Messenger, Whatsapp, Telegram and Twitter. Most of the other apps that I hibernate are those that start on boot and I want to keep sleeping, but they don't take up as much of my battery.
[Xposed General] _Vegas:
Guys you can use "prevent running" instead of greenify, it's awesome.?
[Xposed General] danman7:
So, Nexus 6 running Pure Nexus MM (11/13 build). I install v78 and it's been at the animated boot screen for 45 minutes. Is this normal? I had read it would take a while for the first boot, but this seems excessive.
[Xposed General] g2uzer:
your in a boot loop, reflash uninstaller or dirty flash ROM again
[Xposed General] danman7:
Or, just wipe and restore system from recovery.

Are there any theories as to what would cause said bootloop? I checked and I have 880 mb free on my System partition. That seems like plenty of space, but I don't know how much Xposed requires.
[Xposed General] drewski_1:
I freed up about 40mb and still have most of that after Xposed install, so space is not your issue.

Sent from my Moto X
[Xposed General] Lemagex:
It doesn't work on Purenexus for me either. It works on Cataclysm though, and Xtrasmooth
[Xposed General] g2uzer:
It does work, I'm running it on the latest PureNexus ROM on my Nexus 6 no problem
[Xposed General] Israel_Cohen:
model: h815

xposed: sdk 78 - arm64

Result: bootloop
[Xposed General] Saf8888:
I've tried to install the arm zip on my Nexus 5 / Marshmallow

and iv'e got this infamous error "executing updater binary in zip error"

should i use arm64 zip file?

any suggestions...

EDIT: found out that iv'e used sdk version 21, instead i should've used 23 version. Silly me...
[Xposed General] aliguu:
For stock nexus 6p that's on marshmallow, should I use:

arm or arm64 version?

Which sdk version? 21-23?

And is the installation steps as below?

1. Flash .zip from custom recovery

2. Install .apk

3. Profit?!
[Xposed General] Mr-Glass:
6p is arm64 - marshmallow is sdk version 23 - the steps look correct
[Xposed General] marconiglio:
... Each one thinks to be right

Never mind

Peace and unity [emoji23] [emoji23] [emoji23]
[Xposed General] aviraxp:
Generally, https://github.com/android/platform_frameworks_base/commit/186af6a4e5a79915ef2917393d36a3266e261f81 causes the issue. You can adjust it to your rom, and won't cause any side effects.
[Xposed General] Ibuprophen:
I was able to get the Xposed installer to work but, i did notice when i installed a module (any module) and then activate the module within the installer, i restarted, it was then that CM just hangs on the splash screen (the blue guy on the center).

I feel that something hangs up the boot process when a module is installed and activated.

I'm trying to figure out what went wrong.

I'm stuck with the CM13 Nightly dated 08 November. I cant use the 2 newer nightly releases because of the hanging boot issue.

I have a D2VZW (Verizon Galaxy S3) rooted & unlocked with the latest TWRP.

I also tried 3 different release dates of Open Gapps to see if that may have been the culprit but, i feel that the Open Gapps are fine and not affecting Xposed at all.

Any thought's?

Peace and Love!

Peace and Love!

In addition, i personally don't see any permission issues within the app settings though it could be a permission issue elsewhere...

Thanks!
[Xposed General] Phrodini:
This issue is present in all frameworks or just the newer 86?
[Xposed General] tamaraxxx:
It's not the framework that causes the problem, it's the Android update of November.
[Xposed General] Ibuprophen:
The 86 framework installs and works fine.

I feel (though i could be wrong) that it has something to do with the Xposed installer activating modules (something in that process) that causes the issue.
[Xposed General] bdwilk:
Try the 3.0alpha installer and see if that helps.
[Xposed General] Phrodini:
On ressurection remix ROM with November patch xposed still works. The person who did have an issue said he updated his bootloader to the newest and its fine now.
[Xposed General] Blackscorpion3:
The issue has nothing to do with the xposed framework. It's added code that CM implemented. I am in the process of narrowing down what code it is and reverting the commit on my personal Rom. When I figure it out I will post here which commit it is.

---------- Post added at 07:56 PM ---------- Previous post was at 07:51 PM ----------

Last I knew RR has not been updated to the newest Security patch as the last build was on Oct. 8th meaning it would not have the November Security patch.
[Xposed General] Ibuprophen:
Just an FYI... Cyanogenmod stated in a message that this is not a CM issue but, an Xposed issue...
[Xposed General] Blackscorpion3:
Everyone points fingers at the other. I truly believe it has to do with some new commits CM did. And, if I am wrong then I am wrong.
[Xposed General] Mayex:
The problem is in November security path, so the problem is in Android code
[Xposed General] Blackscorpion3:
Which is precisely what I was saying....
[Xposed General] sdeft:
I am on RR with november patch and it doesn't work. I get bootloop after I module activation.

Tried SELinux to permissive and also older xposed but problem is still there.
[Xposed General] Phrodini:
The one by Neo?
[Xposed General] CRXed:
You kinda did, but it's not CM code, thus CM is rightfully claiming it's not a CM issue.

Am am not even using CM, just the stock ROM and it has the same problem.

So reverting it in CM will not help those running a different ROM. This needs to be fixed in Xposed itself somehow.
[Xposed General] NetDwarf:
Is [MENTION=4419114]rovo89[/MENTION] aware of the current situation? :)
[Xposed General] rovo89:
Yes, since today: https://github.com/rovo89/XposedBridge/issues/129

Don't expect a quick fix for this...
[Xposed General] Lord. Tech:
[MENTION=4419114]rovo89[/MENTION] Sir, You the real MVP.
[Xposed General] Bad Bimr:
I have a Nexus 6 running Stock 6.0.1 (MMB29Q) ROM with Xposed (v86 and 3.1.1). All working 100%. Yesterday I decided to flash the newest factory image of 6.0.1 (MOB31K, Nov 2016). I can flash Xposed with no issues. I can install the installer and again no issues. If I activate a module I get a boot loop. Only solution is to uninstall xposed from recovery. Anybody else having this issue? Did Google do something in the newest version of 6.0.1? All help will be appreciated.

Thanks

BB
[Xposed General] AndyYan:
For the record, rather than attempting to revert the whitelist commit (which gives me conflicts that I don't know how to resolve), I'm attempting to add /data/app to the whitelist by manually editing core/jni/fd_utils-inl.h in android_frameworks_base. Will do a test build to see how this goes and update you guys.
[Xposed General] DKnightX91:
It'd something to do with the newest November security update. They are already looking into a way to patch Xpose from what I read
[Xposed General] Bad Bimr:
Should I flash back to an earlier build of 6.0.1? Which was last working build?

Should I wait it out? When released, where would the patch be found?

Thanks

BB
[Xposed General] DKnightX91:
Well from looking at this:

I would say go back to an older build. Anything before the November 5th security update.
[Xposed General] AndyYan:
Well the 1st attempt failed... From the log it does seem that I have to explicitly put the app's APK itself into the whitelist, which of course means any new module or update to an existing module will add a path outside it and require a rebuild of the ROM itself - unacceptable. I'll see if there's anything else I can do...

EDIT: Seems like the whitelist judgement function is in the same file:

static bool IsWhitelisted(const std::string& path) {
for (size_t i = 0; i < (sizeof(kPathWhitelist) / sizeof(kPathWhitelist[0])); ++i) {
if (kPathWhitelist[i] == path) {
return true;
}
}

static const std::string kFrameworksPrefix = "/system/framework/";
static const std::string kJarSuffix = ".jar";
if (path.compare(0, kFrameworksPrefix.size(), kFrameworksPrefix) == 0 &&
path.compare(path.size() - kJarSuffix.size(), kJarSuffix.size(), kJarSuffix) == 0) {
return true;
}
return false;
}

Let's see what will happen if I just make it return true all the time...

// F_CK GOOGLE - JUST WHITELIST EVERYTHING ALREADY
static bool IsWhitelisted(const std::string& path) {
return true;
}
[Xposed General] sdeft:
no g3 ...own build based on official sources
[Xposed General] otyg:
yeah same bootloop problem on Samsung Galaxy Tab Pro 8.4 w/official CM13 builds, activating any module causes device to get stuck in boot logo
[Xposed General] AndyYan:
2nd test complete and successful - device booted with all Xposed modules enabled!

For ROM builders: manually edit frameworks/base/core/jni/fd_utils-inl.h, find the method IsWhitelisted():

static bool IsWhitelisted(const std::string& path) {
for (size_t i = 0; i < (sizeof(kPathWhitelist) / sizeof(kPathWhitelist[0])); ++i) {
if (kPathWhitelist[i] == path) {
return true;
}
}

static const std::string kFrameworksPrefix = "/system/framework/";
static const std::string kJarSuffix = ".jar";
if (path.compare(0, kFrameworksPrefix.size(), kFrameworksPrefix) == 0 &&
path.compare(path.size() - kJarSuffix.size(), kJarSuffix.size(), kJarSuffix) == 0) {
return true;
}
return false;
}

Change the last "false" to "true" so that it whitelists everything. Save, commit, build. This should be easier than trying to revert all future whitelist-related changes.

This is a ROM-side workaround - it'll have to do until a fix to the Xposed framework itself drops, which could take another while.

EDIT: Here's [MENTION=4898097]arter97[/MENTION] 's patch with more security - just pick this instead of my dirty solution. Sorted out the issue on my own, yet still got heavily outdone :/
[Xposed General] sdeft:
Managed to get a working xposed RR with november security patches by using below commit on my self-built RR.

https://github.com/HealthyMarshmall...mmit/0b5f4e5f762d4d8a85cab1a3085bf4296a97c4e5
[Xposed General] JimTimmler:
Bootloop cm13 s3 i9300

Hi there,

with latest cm13 nightly (cm-13.0-20161114-NIGHTLY-i9300) I got a bootloop too on my device (i9300) with xposed-v86-sdk23-arm.

So what are the opportunities? Waiting for V87 or waiting for changes in cm13? Or is there any workaround to avoid the bootloops?

---------- Post added at 10:21 AM ---------- Previous post was at 10:19 AM ----------

Hi,

Can I use this for my case? And if so...how?
[Xposed General] AndyYan:
The fixes we posted are only for ROM builders. Either you build it yourself, or wait for an unofficial build, or wait for a fix on Xposed's side. CM likely will never merge it officially - they seem to be against Xposed since the beginning.
[Xposed General] JimTimmler:
EDIT: was answered above
[Xposed General] IMTLD:
is there a simple explanation to apply arter97 to a self-built cm? cannot I just edit the specified file and then dirty flash?
[Xposed General] AndyYan:
It's in the source as plain code, but in the ROM as a compiled binary. If you mean you also build yourself, then just cherry-pick that commit should be enough, but modifying the corresponding file would also do - in fact that's what I did today (remember to stage and commit changes afterwards); otherwise no way to apply to an existing ROM.
[Xposed General] NetDwarf:
I don't even expect a fix. It's just important that you know. Thank you anyway. :)
[Xposed General] sdeft:
I made one RR with arter97 mod but got bootloop after module activation.
[Xposed General] ZerNico:
I guess a Xposed update will fix it but the CM could also do something about it.. Whoever comes first

---------- Post added at 06:30 PM ---------- Previous post was at 06:25 PM ----------

Let's hope its fixed pretty fast

Yeah the new Security Patch broke xposed...
[Xposed General] jeepcook:
Download last RR rom, the patch is implemented and xposed works like a charm!!

Envoyé depuis Tapatalk
[Xposed General] Ibuprophen:
Well [MENTION=4419114]rovo89[/MENTION] and others are currently working on it. I've been watching their progress and though it may take some time, they are making progress.
[Xposed General] sdeft:
don't think so...nothing was commited regarding this on RR's git
[Xposed General] jeepcook:
I use it and it works (ks01lte) !! here is the comment from Eliminator, but perhaps only for ks01lte....

Re-uploading ResurrectionRemix-M-v5.7.4-6.0.1_r74-20161113

- november secuity patches

- setup wizard fixed

- xposed compatibly fexed
[Xposed General] sdeft:
yes I guess he is using own fix or the ones mentioned here as there is no official fix from RR team (and probably will never be).
[Xposed General] LuciferIII:
Guys i hear the security patch broke xposed for N ?

Is this a sign for future problems?