yashsingh1/xdaforums huggingface dataset:
[Xposed General] dark_knight_95:
In xposed installer it says xposed installed but not active this happened after installing twrp 3.0.0.I had swiped to the initial read write stuff that it said .I have SDK 23 vs 80 installed also su version is 2.65

Here are my logs

02-24 07:41:01.536 I/Xposed ( 255): ----------------- 02-24 07:41:01.536 I/Xposed ( 255): Starting Xposed version 80, compiled for SDK 23 02-24 07:41:01.536 I/Xposed ( 255): Device: Moto G (motorola), Android version 6.0.1 (SDK 23) 02-24 07:41:01.536 I/Xposed ( 255): ROM: cm_falcon-userdebug 6.0.1 MMB29T 8a3e311177 test-keys 02-24 07:41:01.536 I/Xposed ( 255): Build fingerprint: motorola/falcon_retbr_ds/falcon_umtsds:5.1/LPB23.13-56/58:user/release-keys 02-24 07:41:01.536 I/Xposed ( 255): Platform: armeabi-v7a, 32-bit binary, system server: yes 02-24 07:41:01.536 I/Xposed ( 255): SELinux enabled: yes, enforcing: no 02-24 07:41:04.307 E/Xposed ( 255): Found /data/data/de.robv.android.xposed.installer/conf/disabled, not loading Xposed 02-24 07:44:03.598 F/libc ( 3554): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x74 in tid 3570 (Binder_2) 02-24 07:44:03.599 I/DEBUG ( 242): property debug.db.uid not set; NOT waiting for gdb. 02-24 07:44:03.599 I/DEBUG ( 242): HINT: adb shell setprop debug.db.uid 100000 02-24 07:44:03.599 I/DEBUG ( 242): HINT: adb forward tcp:5039 tcp:5039 02-24 07:44:03.656 E/DEBUG ( 242): unexpected waitpid response: n=3570, status=00000000 02-24 07:44:03.656 E/DEBUG ( 242): tid exited before attach completed: tid 3570 02-24 07:55:15.891 I/XposedInstaller( 6978): Downloaded http://dl.xposed.info/repo/partial/7234.xml.gz with status 0 (error: null), size 18220 bytes 02-24 07:55:16.088 I/XposedInstaller( 6978): Updated repository http://dl.xposed.info/repo/full.xml.gz to version 7247 (1 new / -1 removed modules

Guys please help me
[Xposed General] Lukest85:
To re-enable xposed framework delete /data/data/de.robv.android.xposed.installer/conf/disabled then reboot
[Xposed General] siealex:
Sometimes my phone does not boot after installing Xposed. Logcat displays that it reads classes from all modules and that's all. Galaxy Nexus, 6.0.1, Xposed v80. The same bug was present also on 5.1 with all versions of Xposed. WTH?
[Xposed General] markastor:
I have Xposed not working at LG4 stock-based roms.

I don't what the problem could be, but here is my View attachment error.log.

Thanks for any help.

Btw dont have /conf/disable file.

P.s.: xposed installer says Im fine, but nor modules are working.
[Xposed General] magnamentis:
that hints to a module if it happens for long throughout versions as well as across API versions that's my suspicion (guess without further proof )
[Xposed General] nplezka:
I don't really know if it's Xposed fault, but I'm on a Motorola Moto X Play (stock firmware), and I often found issues with network signal: on some reboots I get "emergency calls only" and I can see network again only after some reboots (or maybe one, it's totally random). I thought it's framework fault because I didn't get this problem when I was on clean Marshmallow (so without Xposed).

It's really annoying and I saw nobody talking about this strange problem.

I saw logs and there is something talking about Motorola Network Controller.

[MENTION=4419114]rovo89[/MENTION] maybe you can have a look...

EDIT: I have "AOSP signal icons", but I had this problem also before installing this module...
[Xposed General] siealex:
Does it happen after pulling out battery?

---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------

It happens with almost any set of modules, but two modules are present always, they are MinMinGuard and GravityBox. And this bug happens with any versions of these modules.
[Xposed General] grep_i:
You have a lot of modules installed it might be possible one or more are not compatible with your rom in your log you see a lot of crashes.

You could try to disable all modules, see if it works and if so first enable gravitybox, reboot and see if everything keeps working and if so enable another module, reboot and see if it keeps working.

I guess you catch my drift now in this way you can find the incompatible module.
[Xposed General] scarline:
NFC Bootloop 6.0.1 xposed v80

Hey, I have the NFC bootloop issue with a brand new Nexus 6p.

What I've done so far:

1. Flashed MMB29Q

2. Flashed TRWP Recovery 3.0.0 angler

3. Installed SuperSU BETA-SuperSU-v2.67-20160121175247 (all fine until here)

4. Flashed xposed-v80-sdk23-arm64.zip ---> Get NFC Loop

I also tried:

1. Flashed MMB29Q

2. Flashed TRWP Recovery 3.0.0 angler

3. Installed SuperSU BETA-SuperSU-v2.67-20160121175247

4. Installed XposedInstaller_3.0_alpha4.apk (all fine until here)

5. Flashed xposed-v80-sdk23-arm64.zip

---> Get NFC Loop

Changed SuperSu to multiuser-support, trust for systemlevel applications and activation during boot in the options had NO effect.

I did hear that flashing xposed > do factory reset, cleaning data > install xposed installer > flash SuperSU could be a possible way that works. Does anyone have experience on this? Does it make a difference when the reboot is done by the xposed-installer?

Many people have his issue, so it must be related to the more recent versions. Is there a confirmation that v78 is working better and without FC for NFC and gaps? Is there a workaround? I would like to install xprivacy...
[Xposed General] netinetinet:
Same here Nexus 5x
[Xposed General] netinetinet:
xposed 78 sdk 23 arm64 work on Nexus 5x
[Xposed General] RMarques:
How should I update framework from V79 to V80?

Inside the module, the update option is deactivated. Should I flash it?

Sent from my LG-D855 using Xparent Skyblue Tapatalk 2
[Xposed General] grep_i:
Just reflash system.img or update everything in Google play store after flashing ROM. Also reflashing complete rom is an option this will fix your problem with 99% probability.

Further v80 does work there are a lot of others here that got it working on the same device.

Also I got myself this problem once with v78 but was fixed for me with above procedure reflash system.img

So my advice would be flash ROM boot up system.

Flash twrp custom recovery through using adb and fastboot manually if possible and afterwards use buttons to start directly the installed custom recovery, if you don't understand what is said. Than take the easy way and flash custom recovery the way you know how and boot to recovery afterwards.

Flash Supersu boot up system.

Flash the framework bootup system and install installer.apk

If you after all this still keep having problems with Google system apps crashing try to see if your device's system volume is not out of space. If so free some space by removing unwanted languages and or apps like Google fit but be careful what to remove and use common sense.
[Xposed General] scarline:
You mean (?):

You mean (?):

1. Clean install

2. Flash recovery

3. Flash SuperSU

4. Flash Xposed

5. Install Xposedinstaller

6. (Dirty) Reflash of system.img

Possible Problem here between step 4-5 is that I will get the loop again. Can I flash Xposed, reboot DIRECTLY to TRWP and reflash system.img BERFORE installing Xposed to prevent the stuck in the loop?

Has anyone made experiences on flashing xposed and directly afterwards doing a factory reset?

---------- Post added at 01:10 PM ---------- Previous post was at 01:09 PM ----------

Have you tried changing SuperSU options and a factory reset directly after flashing xposed?
[Xposed General] Sandivisi:
iam using cyanogenmod 13 nighty on moto g (2013) and i want install xposed on my rom. but i have question, if iam update cyanogenmod 13. do i need flash xposed again every iam update my rom? thx
[Xposed General] markastor:
Any help maybe? ;)
[Xposed General] scarline:
My experience is that things are the other way round. Many are complaining about this problem.

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

When you do the update by flashing a new rom via TRWP over the old one you will defiantly have to reflash the xposed zip.
[Xposed General] grep_i:
OK I guess you're right I whatsoever and most of my friends had no issue with it.

Maybe it had something to do with the transition from version 5.x firmware to 6.x in my case it only happened during upgrading from 5.x to 6.0 and during that time v78 was available so in my case I would have to blame v78.

But I reasoned it had something to do with my system volume so I flashed only system.img again and of course Xposed framework v78 as soon as I saw that the issue was resolved by reflashing system.
[Xposed General] scarline:
Can you please be precise of what was done in which sequence by you? I've heard that some guys make that work by using v78 with an 6.0 Android. [MENTION=4419114]rovo89[/MENTION] is this part of your roadmap? Actually I was a litte bit wondering, because nexus devices are the basement of many developers like the exposed framework is.
[Xposed General] Prattham:
Does anyone has v79 amr64 file link please?

Help is greatly appreciated.

Cheers ?
[Xposed General] Prattham:
[/COLOR]

Here you can find the packages

https://xenserver.underpants-gnomes.biz/~romracer/xposed/[/QUOTE]

Thank you so much :)
[Xposed General] scarline:
You went more or less exactly the way I did. I work on ubuntu with the latest sdk directly from google due the android-tools fastboot and adb are a little bit outdated in the offical repos. The biggest difference I see is, that you did flash xposed first, and during the same trwp session supersu. As I mentioned before, I did flash SuperSU before, rebooted, activated the three options that were deactivated in the SuperSU menu. Additionally I deactivated the NFC because some folks mentioned that did the trick. Personally I do not believe that this procedure will fix my problem (based on my experiences made last night). I could imagine that there is some major-difference because we use different hardware. It would be perfect when other people share their experiences on this with the very same hardware and builds for twrp, supersu, exposed.zip and exposed.apk and of course android.
[Xposed General] grep_i:
You did not read the post very well if you did you could see that supersu was already installed by the time of the piece you quoted. That piece you quoted mentions that you do not have to choose to let TWRP install it's own supersu because version 2.8.x did this when trying to reboot, it detects no supersu because it was systemless I guess and twrp is expecting a system root. And in my example I the supersu used is systemless so if your version of twrp is 2.8.x it is very likely to happen to you too. That's why I mentioned it.

Also the only real difference I see is the used hardware of yours is newer than mine and x64 mine is 32
[Xposed General] scarline:
I obviously mixed that up. But that means we did it the same way. I used twrp 3.0.0 which never asked to root for me.
[Xposed General] magnamentis:
the problem is your OS, sorry if that sound short and cold but that's the answer to your question. ckeck if there is a version specifically for

LG stock, i think i've been reading something but am not enough into that to tell for sure.

only thing i know is that form 10 people with your problem 8 have LGG4 or MIUI stuff, while it was similar for TW users they obviously have found their ways by now.
[Xposed General] grep_i:
No problem, the only thing I can think of is that your system volume has not enough space left can you check the free space of system volume
[Xposed General] scarline:
I never did this with a nexus. On my Samsung I could use heimdall to print the partition table. Whats the way to go with A Nexus? For additional info: I've purchased the 128 GB version. But I' am not sure if this affects only the userdata-partition?
[Xposed General] grep_i:
Yes you're right it only affects user data

The easiest way since you are using Linux is:

Open terminal

Type

adb shell

df -h
[Xposed General] jeftt:
So, I had Xposed framework running fine on my Nexus 6p but reverted to a backup and now can't reinstall the framework.

Installed xposed-v-80-sdk23-arm64.zip via TWRP and the xposed installer apk, after doing a full backup. Installed GEL settings and a few other apps.

I decided to revert to my backup as I was having a few issues with apps after and thought, why not just go back, do it afresh and then install things one by one to find the conflict.

So I wiped everything and restored my backup.

Now when I try to install the exact same xposed framework via twrp I get this error code:

chown: /system/bin/dex2oat.orig.gz: read-only file system

And the install fails....

Anyone got any ideas?

Edit -

Found someone else with exactly the same problem, but no replies to his post

http://xdaforums.com/xposed/help-t3252083
[Xposed General] scarline:
Is the Android-Build the same as it was before?

When you have a complete nandroid-backup, you could try to format everthing with trwp, install a clean and fresh build from google and than do just the restoring process with you data & personal data partition.

The alternative would be to do a clean install and just restore your apps and app-configuration files with titanium-backup directly from a nandroid-backup. Normally its possible to get your personal data with an computer from the internal storage so reflashing the userdata.img is not essential.

Hope this helps!
[Xposed General] magnamentis:
did you try to change permissions to read/write for the file system that is mentioned in the log ?
[Xposed General] Jprime1:
This never happened to me before, but recently the battery icon didnt "drain" in color as the % went down. Reboot didnt fix. Eventually it just started to work. Anyone else?
[Xposed General] jeftt:
I didn't, that's why I'm a little flummoxed.

---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------

I've been contemplating this, may be my only option unless someone else can throw light on why/how the error has occurred and a solution around that.

Thanks for your help.
[Xposed General] ROMfan:
i am getting error 255

using xperia s marshmallow
[Xposed General] _Sparks:
Is Xposed stable on Marshmallow? What are your experiences?

Would specifically like to know about how it works on Nexus 6 if possible.

Sorry, really haven't got time to test it out myself properly, but wouldn't mind taking the time if it works smoothly.
[Xposed General] Nergal di Cuthah:
Work fine for me and others, but it really comes down to a per device thing; so many factors might make it stable or unstable just as it was with xposed lollipop, kit kat, jellybean etc
[Xposed General] RandomPooka:
Works great. Pull the trigger
[Xposed General] joeyakaspce1130:
I'm on an S5 for T-Mobile on CM13 and its running 100% perfectly. Literally, not even 1 problem/issue/FC since I installed it!
[Xposed General] magnamentis:
sounds like those who have all the time to spend money but are too lazy to earn some

however for the sake of it, shoot ahead, no issues while the device is not what matters but the rom and other mods, while all what i just said in

a few words can be found in 10 seconds with a search. ( lower right corner of this page )
[Xposed General] grep_i:
Yeah it's stable are you too ?
[Xposed General] asdfasdfvful:
Hi all,

I'm attempting to create a module for theming, but I'm almost pulling my hair out due to a few things:

1. It seems like anything I do with resparam doesn't work, even if I do exactly what some open sourced modules do

2. It seems as though my XSharedPreferences aren't working. They were at one point, but now I have no idea what is stopping it.

If anyone could help me get this started, I would be extremely grateful. I have no idea what is causing my issues.

Here is my source.

Regards.
[Xposed General] morphmk:
How can I upgrade to the latest version?

I have an HTC One M8 and I'm currently running version 79 but I see that there is a newer version 80 available.

How can I upgrade?
[Xposed General] Nergal di Cuthah:
Flash 80 on top of 79 using recovery or adb
[Xposed General] moejay90:
Guys! Please check this out, this is an enigma not even an issue or error, am running Pure nexus MM, nexus 4 (mako), running latest TWRP with the (usb OTG) options, tried to flash SDK23 - v80 - ARM. Zip and it gave me this error, even on my previous rom which is ressurection remix ROM 6.0 MM, I don't understand how this situation can be solved, experts! Please enlighten me!
[Xposed General] morphmk:
Should I wipe dalvik / cache after flashing?
[Xposed General] moejay90:
It's recommend that you do so.
[Xposed General] Nergal di Cuthah:
I do, some people don't. most people in this thread who report that they do tend to find it helps when a previous non-wipe situation occured (though that could be coincidental as the reflash may itself be the reason for function).
[Xposed General] siealex:
Downgrade to TWRP 2.8.7.0 or lower.
[Xposed General] moejay90:
Thanks for your replay but u see the thing is when i flash the twrp image to downgrade, it either fails or says flash is complete and when I boot into recovery its still the latest twrp, I don't get it why would the latest twrp have an error flashing the zip?
[Xposed General] magnamentis:
hard to tell, try another recovery first, if it doesn't helpe delete 1 or two gapps from system just incase that your system partion would be full

happend recently, especially with stock marshmallow and depends on which gapps package (size) you have installed.

BTW latest twrp is not a valid term, have seen too many times people stating the lates while they only missed that there was an even later one, always mention the version number. 2.8.7.x works well, 3.0.0.x produces errors for some users.
[Xposed General] moejay90:
Thanks for your replay bro, with regards to Gapps, I only have the mini Gapps i will check the size, but i do indeed have CM13 roms backed up in my internal storage as well as resurrection remix rom, so you think that plays a role in the partition?
[Xposed General] magnamentis:
i really can't tell, i was just sharing a few thoughts based on recent reading and considering the fact that there must be a reason after all.

i doubt it's the full partition then, if i remember correctly that would produce error 255 but again, you have to play a bit, trial and error so to say :)

after all not much can happen that one would have to regret IMO :) good luck
[Xposed General] moejay90:
Thanks a lot bro! I really appreciate it, i will get on that and start working and see what happens! Perhaps move the back ups to my pc and do it all over again, however it's really really Odd! I mean the Error Code is 1, which i never seen before in my life at least not in TWRP.
[Xposed General] magnamentis:
i found only one kind of mistake leading to this error which is "wrong rom for wrong device" not saying it's the case, this is just the only

thing that i found causing error=1 in twrp. perhaps you check your download quickly, not only version but perhaps redownload, could be a bady :)
[Xposed General] moejay90:
Could it be?? (mako) nexus 4 is SDK23-v80-ARM. Zip running mm l, any corrections?? To the zip file?
[Xposed General] dreko2000:
I have â rooted HTC a9 unlocked USA model with Android 6.0.1. Which xposed version can I use ?

HTC One A9 cihazımdan Tapatalk kullanılarak gönderildi
[Xposed General] mayyhem84:
Hello!

I bought the one M8 dual sim - it has the android 6.0, the 6.16.401.101 version, compilation CL675548.

It is a stock ROM, with stock recovery, but rooted. it is S-ON.

What I am doing:

1) I've downloaded the xposed-v80-sdk23-arm.zip, from http://xdaforums.com/show....php?t=3034811

2) went to the recovery, fastboot

3) connected to the PC, in CMD fastboot boot C:\twrp-2.8.9.0-m8.img

4) on the phone I click install and point to the xposed-v80-sdk23-arm.zip

5) it is installed, the I click reboot system

6) the system is rebuilding the apps and when is finished it shows info that the system UI crashed - I can choose to send report or not. I can choose whatever - it is showing that message all the time.

I am quite sure, tha I am having enough space on my device to make it istall.

I can not find any solution for that :(

Please help!! I rly need xposed.. ;-(

thank You in advance!
[Xposed General] grep_i:
V80 sdk23 arm

---------- Post added at 04:11 PM ---------- Previous post was at 04:03 PM ----------

This question comes by a lot of times on this forum and a lot of suggestions on what to do are on this forum try to search harder.

Also I'm pretty sure you need to be S-off to make anything happen on your device it means your device is unlocked and you can write to the devices NAND.

Saying you have enough space and doesn't come up with facts about it doesn't help you.

For all we know it is even possible you are talking about the space on your SD card instead of your /system volume.
[Xposed General] dreko2000:
Thanks for the answer. I am s-on also, can I flash xposed?

HTC One A9 cihazımdan Tapatalk kullanılarak gönderildi
[Xposed General] grep_i:
That must be possible absolutely be sure to pick v80 SDK 23 arm
[Xposed General] dreko2000:
Thanks again. V80 sdk23.arm.zip or V80 sdk23.arm64.zip for unlocked USA model ?

HTC One A9 cihazımdan Tapatalk kullanılarak gönderildi
[Xposed General] grep_i:
V80 sdk23 arm as I said before
[Xposed General] mayyhem84:
true, but I can not catch right answer :(

->some are saying that it can be from default launcher-i've hanged it to nova as it was written in some threads-no result.

->I've checked the free space- /system volume - I have more that 700MB free (the device has 16GB build in memory). I was not referring to SD card - there is no data.. yet :)

I am wondering if that can be the S-ON issue - but as I read - some say it can, some say it can not - try to be wiser ;) i can not find anyone that could confirm that :/

I am wondering - can it be the case, that I am not using the installed twrp but I am just launching it by PC?

reading that article we can assume that yes, but this is out of date? Or can I use that solution to s-off my device?

somewhere i've found that this can be an alternative for the s-on?

I am getting more and more confused.. :eek:
[Xposed General] moejay90:
Bro there is no way in he** it can be done with S on, it just doesn't add up, S off is your solution.
[Xposed General] jeftt:
I followed Curiousn00b's advice in my other post about my problem and dirty flashed my rom again. It solved the problem and Xposed framework has now re-installed.

http://xdaforums.com/xposed/nexus-6p-xposed-framework-wont-reinstall-t3323424
[Xposed General] grep_i:
That advice is all around this thread but I'm glad you found out how to this.
[Xposed General] moejay90:
With that being said have you checked the materialized xposed installer app! Its smoking hot! U might wanna try it.
[Xposed General] magnamentis:
that sounds right SDK23=marshmallow _ ARM is for 32bit hence also correct, no clue what else that could be, did you try another recovery ?
[Xposed General] jeftt:
I'll go check it out, thanks for the heads up.
[Xposed General] moejay90:
Sure thing, Hope u like it buddy.

---------- Post added at 01:27 PM ---------- Previous post was at 01:24 PM ----------

Bro I have solved the issue, see the thing is I had ressurection remix rom official build 5.6.4, on that Rom it didn't work but on pure nexus marshmallow it did! So your explanation to the error code was correct and in place! Well done man thanks a lot to your help, you are the only one in the whole XDA that actually gave me the only and right solution!!
[Xposed General] grep_i:
As I can see the answer is giving many times by a lot of people maybe you should learn to read better or understand better what people are telling you.

Besides that I'm glad you finally found out how to fix the problem.
[Xposed General] moejay90:
Thanks, I did indeed understand and comprehend what people said as am not new to the Android development business, however the solutions posted were irrelevant to the code error which I had. Thanks.
[Xposed General] mayyhem84:
actually I am not so sure about it...

here they say about s-on - but just are flashing the zip, not changing to s-off..

on the other side it looks like that is the case..

well - need to s-off and see if that is true :) thx for response!