yashsingh1/xdaforums huggingface dataset:
[Xposed General] EVOuser94:
When trying to flash version 86 in TWRP, causes bootloops, when trying to flash via app I get this error.

Sprint HTC 10, s-off, rooted, running Bad Boyz latest custom Rom.

Anything I can do to get this working?
[Xposed General] EVOuser94:
Appears it added a file aswell that doesn't get deleted with uninstaller.

App_process32_xposed
[Xposed General] Ok_Kaleidoscope5109:
REflashed both CM13 and OpenGapps. Problem still persists. I can't imagine what's hijacked my system. I did a full wipe and now it's working again but I'm still curious HOW this was an issue to begin with....
[Xposed General] lovebirdi:
Getting random app crashes/freezes after flashing xposed 86 on CM 13 Galaxy note 3 N900 exynos
[Xposed General] clvelizq@gmail.com:
any help

:crying:Xposed is not (yet) compatible with the version sdk 23 or processor architecture (armeabi-v7a)

CAN NOT LINK EXECUTABLE: library "libdvm.so" page not found for 0x0b6f3002c record was not found (block_size 16)

CM13 upgrade came after that mistake before worked smoothly
[Xposed General] Hawtpants:
Xposed not working on the Moto Maxx using BHB27's RessurrectionRemix rom.. Infinite bootloops when trying to either flash the v86 zip or using the installer. Any help?
[Xposed General] grep_i:
You have old installer apk package download new one from this forum.

Lowest version that works is 3.0 alpha 4
[Xposed General] matrx10503:
So i'm going to have to completely re-flash my phone now since I have bootloop!!!???

Since this idiotic GS7 has no custom recovery I can't do any uninstaller zip

I can't boot into safe mode....I can't turn my phone off at all......bootloop to AT&T logo where my phone just sits and overheats.
[Xposed General] Super_a_bo:
I would like to know when xposed can be applied to Android N
[Xposed General] Ja_som:
When it will be ready...
[Xposed General] LPW00:
API 24 or API 25 (7.0 or 7.1)?
[Xposed General] shawkes:
I guess a little reading could have prevented that.
[Xposed General] grep_i:
Which version do you have because there is custom recovery TWRP for galaxy S7 available in 4 variety's
[Xposed General] matrx10503:
Yeah...I know

I somehow forgot I was to use the specially made one for my device.

And no, locked bootloader, no custom recovery.

I had to ODIN flash my f/w to get a working phone again.
[Xposed General] bdwilk:
Should've bought exynos.
[Xposed General] grep_i:
TWRP Custom recovery for China Qualcomm devices is available so probably there will be soon availability for other versions of Qualcomm too.

Just be patient.
[Xposed General] bdwilk:
Not for me. I haven't owned a Samsung device in years. I've just read also since the exynos processor is made by Samsung its better optimized than the Qualcomm versions in their phones.
[Xposed General] vrgolin:
hi guys , little help, i have a Note4 6.0.1 MM (N910H) wich ver. of Xpose Framework and .APK i should use? im confuse. thanks in advance.
[Xposed General] bdwilk:
Search Wanam Samsung Xposed.
[Xposed General] Thatoneguyyyy:
When is xposed for Nougat going to get launched Im waiting since two months now , really desparate
[Xposed General] D-m-x:
When it's ready. Also asking for Eta's is rude and forbidden on XDA. Wait some more.

Gesendet von meinem Nexus 6P mit Tapatalk
[Xposed General] todonormal:
It's possible what xposed.apk install in "adoptable storage" in Marshmallow?
[Xposed General] Au5t1n:
Been having an issue with Instagram and thought it was Xinsta module but it seems it may be Xposed. I'm posting some quotes from the Xinsta thread to show how this can be explained...
[Xposed General] Sreyaz01:
Android 7.1 is available for me but waiting for xposed for 7.1 not asking for eta, just waiting
[Xposed General] ldeveraux:
Then there's absolutely no reason to tell anyone that. Wait in silence
[Xposed General] Sreyaz01:
Just sharing
[Xposed General] Ja_som:
But nobody cares...
[Xposed General] ldeveraux:
Your trying to annoy the developer into working harder and faster. People do it every day and it's frowned upon. Let him be so you don't get on his bad side
[Xposed General] grep_i:
Thanks for the info, this really helped ☠

No one cares better don't do it again.
[Xposed General] GidgetTheGnome:
xposed it one of the greatest must have tools, right now im trying to get it to install on my rooted j320az but each time i try and flash it, it just freezes after boot any suggestions?
[Xposed General] bdwilk:
ASUS Z00LD_LG f320s_Lenovo a328
[Xposed General] mrhamed:
Im waiting since two months now , really desparate
[Xposed General] Xp3riaXpr3ss:
Refer to http://xdaforums.com/xposed/unofficial-xposed-samsung-lollipop-t3180960/page558 for more info and possibly a solution.
[Xposed General] boldonc:
Dear rovo89!

What changed in Xposed framework from version 86.3?? Why only Xposed v86.2 work with Safety Net?
[Xposed General] grep_i:
You know that's not rovo89 Xposed but topjohnwu
[Xposed General] boldonc:
Ok, but the question remaining...why only Xposed v86.2 work with Safety Net?
[Xposed General] grep_i:
Because higher versions are for Magisk and at this moment people are reporting that Magisk is being detected by safetynet that's why.

I've read reports of people who still got it working but you can better check the Magisk thread if you want to know more and better.
[Xposed General] EVOuser94:
Would really appreciate some help getting xposed working on my device.

I am S-off....rooted, and on a custom ROM that people have said it works fine on for them. :confused:
[Xposed General] bdwilk:
NOT enough info to get help. What phone? (for starters)
[Xposed General] EVOuser94:
Sprint Model HTC 10, Running on LeeDroids Custom ROM, latest TWRP.
[Xposed General] grep_i:
Tell more about how you flashed what the results were and what's not working and maybe post a log file or screenshot of error
[Xposed General] EVOuser94:
Flashed V86 arm64 via TWRP, caused bootloops, so technically nothing works right now. flashing uninstaller fixes bootloops.
[Xposed General] grep_i:
Have you already tried and ask the question in HTC10 thread or in Leedroid ROM thread ?

If you want answers from here you need to give more information, as it seems you are not capable enough by giving it yourself, you need at least come up with logcat of failed boot but if I were you I would start asking questions in the Leedroid ROM thread first it's quite possible ROM is not even compatible with Xposed.
[Xposed General] EVOuser94:
Last I checked you can't get a logcat of a boot loop... sir I asked assistance here because no matter which ROM I'm using it seems the same issue. There is literally no reason to say I'm incapable of anything, if you alone are unwilling to help me I can be patient and wait for someone who is. What more information can I provide other than an as far as I know impossible logcat.....I wasn't rude, I'm not blaming anyone, I'm not trying to make this a discussion of mine or your intelligence, rather proceed to get the required assistance to resolving my issue....I've used Xposed on many devices prior to this one....
[Xposed General] bdwilk:
http://xdaforums.com/showthread.php?p=47172724

Read this.

<font color="Red">Getting a Logcat during the dreaded Bootloop</font><br />

<br />

The only difference between grabbing a logcat while running and grabbing one during a bootloop is the program you're going to use. Instead of the standard adb bridge, we'll be using the adb monitor tool. You can find this tool under the "TOOLS" folder. Open the "Tools" folder, right click on any empty space and select "Open Command Window Here"<br />

Once the window is open, type "monitor" (without the quotes) and press enter. A whole new program will open listing the device ID and subfolders (your devices partitions)<br />

<font color="red">IMPORTANT! The device ID may not show up right away, THIS IS OK! I found that it took about three bootloop cycles to actually connect.</font><br />

Once you see the device ID, within a few seconds you should see the "system" partition listed underneath. Select it.<br />

Down in the bottom left corner select the "Logcat" tab. From here, you can grab the logcat in a txt format or just watch it scroll.<br />

I have taken screenshots of the process, and are available here<br />

<br />

There's a great guide here that goes a little more in depth and has updated information about the requirements for a log during bootloops.<br />

<br />

<br />

<font color="Red">How to Filter your Logcat</font><br />

<br />

Lets say you want to find only the logs for a specific app or process, searching through thousands of lines can be a pain. Luckily, adb allows you to filter your logs based on application tags!<br />

Here's how:<br />

<br />

<br />

This filter basically says "Show me only logs for ActivityManager at an Information or above level, and all logs for 'MyApp' with a priority level of Debug and higher" The *:S is important here, this makes all other tags <i>Silent</i> so that it ensures only the filtered tags are shown in your log.How's that for handy?<br />

<br />

<br />

<font color="red">Demesg (kernel) Logs</font><br />

<br />

For a demesg log you'll want to follow the same instructions as above to get into adb terminal.<br />

Once there, type adb devices to verify you're connected. Now you can pull a log by simply typing "adb shell dmesg > dmesg.txt" (without the quotatons" <b>This will place the logs in the same folder that you launched terminal from (platform-tools)</b><br />

<br />

Also, for more detailed information and a few other useful commands check out this site

ASUS Z00LD_LG f320s_Lenovo a328
[Xposed General] EVOuser94:
Interesting. Okay well since I have no access to a functional PC that won't work for me, but I'll keep it in mind for when I do.
[Xposed General] grep_i:
I said not capable enough I didn't say incapable.

Also I provided you with some options for you to explore, that's offering help.

It is possible to get logcat of bootloop and I just saw someone posted you instructions on how to do that.

As I told you before you need to give much more information if you are seeking for the right help.

In this case you got the help because of your comment on logcat that was incorrect which you didn't share out of yourself but I had to pull it out of you.

If you keep on sharing information this way it takes people for ever to understand your problem and they will most probably not even answer on it.

Good luck with getting the logcat from bootloop :fingers-crossed:
[Xposed General] ryan456:
I am using le eco 2 and I cannot install zip in rooted phone

My phone is le eco 2

Version-6.0 marshmallow

Please do tell me how can I zip the file and also if possible which zip file is compatible for my device

Also can I zip with flashfire

As I cannot install manually in recovery mode as I cannot see any single file in SD card of twrp recovery .mode

Sorry if any spell errors

Thanks in advance

Hope someone helps me
[Xposed General] Portgas D. Ace:
Quick question:

Did you wipe cache&dalvik after flashing Xposed? This is mandatory, otherwise a bootloop is guaranteed.
[Xposed General] EVOuser94:
Yes I did.
[Xposed General] grep_i:
Not needed Xposed does this already.

I never did it and Xposed is working fine for me even with suhide and root switch.
[Xposed General] Portgas D. Ace:
Okay, so a live boot log would be the only option to have a closer look at your issue.

That's because you use the systemless version, don't you?

Flashing Xposed does not wipe any cache, at least not to my knowledge.
[Xposed General] grep_i:
Yes I use systemless Xposed.

To my knowledge Xposed does this since v86.0 I know this because it irritated me to wait for 15+ minutes after every flash of Xposed for the app optimizations to complete.

That's why I nowadays flash as much as possible in one go didn't do that before because before that time you had to clear dalvik and cache yourself if you needed or wanted it.

I never did this back then and so I was quick up and running after flashing new versions of root, kernel or Xposed starting with version v86.0 the dalvik and cache clear was no choice anymore it was build in the flashing procedure.
[Xposed General] Portgas D. Ace:
I am not sure if this is the case since v86, because I always had to wipe cache&dalvik manually on each of my devices (Samsung S5, LG L90, OnePlus X, Nexus 7), no matter what version (system-based) of Xposed I flashed. Otherwise I end up with a bootloop.

There is also no official statement from rovo89 in his changelog or announcements regarding this issue, so maybe we need more clarification on this.
[Xposed General] grep_i:
My bad it was in the changelog of v85.0 after that time I always updated

ROM, SuperSU, Kernel and XPosed in one go so I did not get 2 or 3 times the recompilation screen.

After that version I jumped in to the systemless wagon so maybe I've got it all wrong.

Although I think it's very weird it is mandatory at all your devices and all Xposed versions it must be something like a custom rom breaking dalvik and cache.

I know for your device Nexus 7 I got it running and flash Xposed without clearing dalvik and cache and no bootloop on stock rom.

Official statement from rovo89:

changelog v85.0
[Xposed General] Portgas D. Ace:
Okay, but from my understanding, this applies only when updating Xposed from a version below v85. A clean flash might still require a manual wipe.

Nevertheless, if it works for you without a wipe, that's good. The good thing is that the systemless variant doesn't require any wipe anymore, so it is also possible to make a clean flash without Xposed and just flash it afterwards. This way it is easier to identify possible culprits of a bootloop.
[Xposed General] Kantirist:
I have a Bootloop on my Honor 7 when i tried to install xposed-v86-sdk23-arm64.zip .. So I download another version (xposed-v84-sdk23-arm64.zip). With that one i have no bootloop but in the xposed installer the warning came that xposed v84 is installed but not activ...

What should I do now? (Sorry for the bad english)

Honor 7 (PLK-L01) B380

Emui 4.0.1

Android 6.0

SuperSU 2.78
[Xposed General] Portgas D. Ace:
Open your Xposed log and check if you find some entry

Found /data/data/de.robv.android.xposed.installer/config/disabled

If yes, navigate to that path by using a file manager with root access and delete this "disabled" file. Reboot and you are okay.

Otherwise post your Xposed log here.
[Xposed General] Kantirist:
I cant find a config folder.. In de.robv.android.x posed.installer folder are only a Cache and a File folder
[Xposed General] reggiexp:
bootloop on v86 on resuction remix cm13 based on my xaoimi

(bootloop when i enable a module)
[Xposed General] Nergal di Cuthah:
Sounds like it's the module's fault, perhaps provide xposed logs to the thread for the module?
[Xposed General] reggiexp:
Nope.

Flashed 84 and i can enable all modules.... 86 has a bug in it... As soon as i enable 1 modules it bootloops
[Xposed General] Nergal di Cuthah:
What module, are you sure it's 86 compatible? Or is it "any module"? 86 has worked fine for me for months (different device though). What about 85? If 85 works check the log for incompatibility with module (will warn that module uses its own api calls instead of call from xposed)
[Xposed General] reggiexp:
I have v86 miui on my xiaomi with miui rom works fine for 6months and my other xiaomi installed reseruction remix rom. And v86 won't work on this rom. I think hr made a error in his coding he updated it 31/10 the v86 module right?

Anyway v84 works so i say on that for now. He needs to fix it. Never had problems with xposed.
[Xposed General] Nergal di Cuthah:
Right but, if indeed bugged, he needs more information: logs, knowledge of what modules, etc. It should be noted that xposed works best on unaltered AOSP and that often CM builds (usually nightly builds though) are known to have issues with xPosed.

But again, just a report isn't enough, you need to provide evidence so rovo can look into it
[Xposed General] reggiexp:
I know. But seems im not thr only one. I just read post and try to find how to fix and v84 works. So yeah i don't do logcat and things cause i have no clue how and what.

I just wanted to say that v86 bootlooped. Why i don't know. But since v84 works i don't mind
[Xposed General] Nergal di Cuthah:
Again imho testing with v85 would rule out the major change made to 86 (module compatibility)

86 rejects certain modules, if said module really wants to start but can't then a bootloop might occur. 85 will warn about module incompatibility but not block the module loading and 84 won't warn. Since 86 installs with no bootloops until you enable a module I can wager the guess that this is the issue. But nobody will know (or fix for future versions) if you don't do the legwork that none can do for you.
[Xposed General] reggiexp:
Ow okay so 85 is better? And won't boot loop? Will try later that then
[Xposed General] bdwilk:
http://xdaforums.com/showthread.php?t=1726238&p=27754634

I use RR sometimes too and I agree with [MENTION=5447130]Nergal di Cuthah[/MENTION] about it supposed to be used on AOSP ROMs. RR is heavily modified in and of itself so most modules (that I've tried) aren't compatible with it. You said yourself you have v86 on MIUI and it works fine. So it's not the framework to blame. It's the combination of ROM and module. Get a logcat. Learn from the link I provided.
[Xposed General] reggiexp:
Okay thanks. Yes but i see this v86 is updated no? On the 31/10? Or did i miss reqd somehow.

Anyway yes i guess it's RR but mine is base cm13 since there is no aosp port for Xiaomi Redmi note 3
[Xposed General] Nergal di Cuthah:
No guarantee but yes that's my theory, that 85 won't.
[Xposed General] reggiexp:
Okay thanks for the help :)
[Xposed General] grep_i:
I think it's the stricter denial of bad modules that's causing v84 to work and v86 not anymore.

V84 will warn but still load v86 will not work it stops.

Try to find out which old not well coded module you have loaded.

Disable that module or ask the developer to update it or search for a working replacement.
[Xposed General] bdwilk:
[MENTION=3259959]reggiexp[/MENTION] I'm just curious, what's your list of modules?
[Xposed General] reggiexp:
YouTube adaway

YouTube background

Amplifier

No Wakelock (not that i use it...)

.... (no idea why there is a xposed module don't even use it)

Greenify

Minminguard (who doesn't seem to work anymore...)

And xinternalsd (who i need to setup for my games)
[Xposed General] Ibuprophen:
The disappearing framework display...

Just a quick, minor, question...

I provided some screenshots numbered & labeled in order.

Does anyone see the difference between screenshot 3 & 4?

Though XPosed is working great, I noticed this little hiccup when changing the theme from light to dark that eventually goes away.

Just an FYI for the Dev...

Thanks a bunch!
[Xposed General] bdwilk:
[MENTION=3259959]reggiexp[/MENTION] that 5th module down is a no-no. We support developers here. (I had a feeling you had that installed) See if that's your problem. Try each module one by one to see which is the culprit.
[Xposed General] reggiexp:
Ah no i don't crack to get free app. That doesn't work like 80% of the time.

I use it to crack waze cause in france it may not say where camera are exactly. Just a zone.

Don't even understand 90% of lucky patcher lol

With all the playstore fake billing who i never understood cause it never worked.
[Xposed General] Ibuprophen:
There are also times that someone has more than 1 module that is trying to accomplish the same things that causes a conflict weather or not only 1 of the features are being used, another unused feature within another module can still conflict with others. Just double check that a feature 1 module is using isn't conflicting with another module that has the same feature.

I hope i explained it okay...
[Xposed General] grep_i:
OK that's great, try to loose

No wakelock & minminguard
[Xposed General] Au5t1n:
An issue with Instagram while Xposed is installed. Not sure if I should post Android bug report or Xposed log.

http://xdaforums.com/xposed/modules/mod-xinsta-download-images-videos-t3077110/post69495874
[Xposed General] reggiexp:
Better mate?

Yeah nan i stick to v84 for now. Way to lazy to flash and reboot and reflash. I will try v85. Soon.

No Wakelock it's useless cause RR has something like that included and i don't even use the module anyway.
[Xposed General] anhtin:
Hi all, I tried to install the framework on Oneplus 3 but I got stuck at the boot logo... please advise...
[Xposed General] Portgas D. Ace:
Please provide more information about your ROM, Android version, files you used and steps you performed.

But let's start with some basic stuff: did you wipe cache&dalvik after flashing Xposed in recovery?
[Xposed General] anhtin:
my ROM: Hydrogen OS v 2.5.3 latest beta, marshmallow.

I asked sdk v86 arm64

I installed the framework after I flashed GAPPs.

I did wipe cache and dalvik after flashing Xposed.
[Xposed General] Portgas D. Ace:
Okay, so the general procedure you performed seems correct. There are two possibilities right now. The first one is to have a look at the OP3 HydrogenOS help threads in the OP3 forum on their web page or the OP3 subforum here on XDA for assistance. The second option would be to capture a bootloop log file via ADB and post it on the Xposed github, so that rovo89 can have a look at it.
[Xposed General] grep_i:
Yes much better but can you please remove it from my quote too.

Look at my post as example

Thanks please.

If you're not in need of systemless Xposed you can stay on older v84 Xposed but keep in mind that there is far less support for older versions because most try to work with the latest versions so help with problems is harder to get.
[Xposed General] bdwilk:
Did you let your system boot up before flashing the framework? Sometimes there's a conflict with optimizing apps and it might help to just flash rom/gapps boot to system then flash the framework separately. You can also install the framework from the newest xposedinstaller apk.
[Xposed General] anhtin:
I did all that but no luck... so I went and tried Magisk installer. It works!!! Thanks
[Xposed General] CRXed:
Xposed v86 bootloops on Nexus 6 November update. (shamu-mob31e)

Going back to September build where it worked just fine....
[Xposed General] Diependennis:
How can i instal xposed on my oneplus2 rooted running on paranoid android 6.0.2 ?
[Xposed General] Nergal di Cuthah:
system rooted or systemless?
[Xposed General] Diependennis:
How can i find out ????
[Xposed General] Nergal di Cuthah:
Maybe ask http://xdaforums.com/paranoid-android/help

Or the thread from where you got the rom

If system based, and you have room in the system partition, you should be able to use the new xposed 3.1 installer and install it from in app.

Off topic side note: always quote the post you are replying to so a conversation can be followed within the larger thread-discussion
[Xposed General] Alexey71:
Latest CM13. bootloop
[Xposed General] bdwilk:
Let me look into my magic ball......

---------- Post added at 08:34 AM ---------- Previous post was at 08:31 AM ----------

If anyone wants any attempt at proper help with an issue you need to provide

1.phone model

2.rom

3.what you flashed

4.how you flashed

5.what happened

6.logcat

7.anything else that could possibly affect the outcome of what you are trying to achieve.
[Xposed General] Alexey71:
http://xdaforums.com/showpost.php?p=69562997&postcount=4339
[Xposed General] bdwilk:
http://xdaforums.com/xposed/discussion-xposed-marshmallow-t3249095/post69564017
[Xposed General] deathscythemeng:
A temp workaround. Just make static bool IsWhitelisted( const std::string& path) always return true in fd_utils-inl.h. However, I have no idea how to fix it in xposed. I am not good at software :(
[Xposed General] Alexey71:
In all of my devices bootloop. If you flash the CM13 officiall of 10 November and above. :(