yashsingh1/xdaforums huggingface dataset:
[Xposed General] arpit_nnd:
I am facing the issue too. :(
[Xposed General] Artim_96:
Uhm... No. That's exactly what I did, everything is working fine. For rooting without any custom recovery the only way for my device is CF's autoroot. After that, I just flashed the v2.76 zip and the XPosed zip through FlashFire and done.
[Xposed General] dimm0k:
since you've started Xposed 86, you've mentioned there was an issue with SuperSU and systemless v86. is this the case here as well and has Chainfire acknowledged? just wondering...
[Xposed General] Guizão BR:
Hi, i have the mt6753 device with Android 6.0, i tried install your xposed version and i have the message: The framework is installed but not active.

I do the log with the app liveboot of chainfire

https://drive.google.com/file/d/0B7ElLhiJhFxybkRUYnZJZjR1aFU/view?usp=drivesdk
[Xposed General] Artim_96:
Tried the tips from the posts a few pages back?
[Xposed General] garthybarthy:
Urm...yes. As that's what he was stating.
[Xposed General] Artim_96:
No. He stated that it wouldn't work if you flash 2.76 over 2.74, but it is working. At least over FlashFire
[Xposed General] garthybarthy:
Good for you then :) other people aren't so fortunate and have issues which he was pointing out.
[Xposed General] Guizão BR:
yes
[Xposed General] Artim_96:
Maybe it's the way FlashFire works. Maybe the installation only restores the original boot.img when flashed through FlashFire but it's not working with recoveries.

But the only errors I'm seeing here are that users don't restore boot.img when switching from 85.x to 86.x and that the installer says it's not activated for some reason.
[Xposed General] SpasilliumNexus:
Managed to get it working. Originally I had the script set up where the zip gets extracted to /tmp/xposed.

package_extract_dir("xposed", "[COLOR="Red"]/tmp/xposed[/COLOR]");
run_program("/sbin/busybox", "unzip", "[COLOR="red"]/tmp/xposed/[/COLOR]xposed-v86.2-sdk23-topjohnwu.zip", "META-INF/com/google/android/*", "-d", "[COLOR="red"]/tmp/xposed[/COLOR]");
run_program("/sbin/busybox", "sh", "/tmp/xposed/META-INF/com/google/android/update-binary", "dummy", "1", "[COLOR="red"]/tmp/xposed/[/COLOR]xposed-v86.2-sdk23-topjohnwu.zip");

I looked in the installer's update-binary and seen that it already extracts to /tmp/xposed (line 38: INSTALLER=/tmp/xposed), so i'm guessing along with my setup, it was extracting to /tmp/xposed/xposed instead of /tmp/xposed, causing the error.

Simple fix was just having the script extract to /tmp

package_extract_dir("xposed", "[COLOR="green"]/tmp[/COLOR]");
run_program("/sbin/busybox", "unzip", "[COLOR="green"]/tmp/[/COLOR]xposed-v86.2-sdk23-topjohnwu.zip", "META-INF/com/google/android/*", "-d", "[COLOR="green"]/tmp[/COLOR]");
run_program("/sbin/busybox", "sh", "[COLOR="green"]/tmp/[/COLOR]META-INF/com/google/android/update-binary", "dummy", "1", "[COLOR="green"]/tmp/[/COLOR]xposed-v86.2-sdk23-topjohnwu.zip");

Hopefully this makes sense.
[Xposed General] saikoz:
did u try flash latest beta supersu?

in my case it fixed my problem
[Xposed General] dimm0k:
if the latest beta is UPDATE-SuperSU-v2.76-20160630161323.zip then yes, I've already tried this...
[Xposed General] topjohnwu:
This makes total sense :)

Thanks for figuring it out
[Xposed General] ddimple4:
Thanks for the tremendous work.

If I have 86.1 working beautifully, is there any reason to move to 86.2?

Would I just flash in place or would I need to remove first?
[Xposed General] -Duir-:
Yes, 2.76 is both the most recent beta and [subsequently became] the current stable release. Which is why I find it interesting that beta worked over the stable release since they're the same version.
[Xposed General] grep_i:
OK but I did flash it over 2.74 but with flashfire because I was too lazy getting up and connecting phone to computer to boot custom recovery to flash manually. No problem at all, so I guess your rom had an issue or you are missing something that prevents you from properly updating SuperSU.

But other than that the text still stays crystal clear to me.

You or anyone having an issue does not make the text unclear, sorry for that.
[Xposed General] garthybarthy:
I wasn't having an issue I'm fine, I was just helping someone else get there point across and explaining what they meant better :)
[Xposed General] dimm0k:
have you tried comparing them? the link for the stable and beta both point to the same link when I open them...
[Xposed General] samwidd:
i am not able to install this material xposed in H2OS OP3 but it did install without any issues in OOS, any ideas why so?
[Xposed General] CrazyCypher:
I read that there are problems with SuperSU with some people, me included... so I restored stock boot and system img and tried to reflash SuperSU and xposed but I always get "xposed installed but not active"... I tried to disable it and re-enable but nothing works... I also see people successfully installing xposed with flashfire, so can anyone please tell me if the option with flashfire will work or I shouldnt bother to try and wait for SuperSU update?

Thank you very much for your answers and kind regards
[Xposed General] Eagle 3:
I just updated my Note 4 N910C to xposed v86.2. I had 85.7 installed before. It installed with no problem.

Here are the steps that I did.

TWRP: Backup everything

Uninstall Xposed Installer

Odin: flash stock rom N910CXXS2DPG2

Odin: flash TWRP = twrp-3.0.2-0-treltexx.img.tar

TWRP: Uninstall Xposed = xposed-uninstaller-topjohnwu-20160718v2.zip

TWRP: install SuperSU = UPDATE-SuperSU-v2.76-SYSTEMLESS.zip

TWRP: install xposed = xposed-v86.2-sdk23-topjohnwu.zip

Xposed Installer = XposedInstaller_by_dvdandroid.apk
[Xposed General] SheridanJohn:
Greetings,

On my Z5 dual, the 86.2 installer complains, that my SuperSU is < 2.76, which is not true. I have the 2.76 installed. On my Z4 Tablet, I have all versions the same (but it uses AndroPlusKernel, while the Z5 is on stock kernel (rootkernel patched, but SU installed from TWRP). There, the 86.2 finds >= 2.76 and happily installs...
[Xposed General] Familotel:
Just installed Xposed v86.2 on OnePlus 3 , OxygenOS 3.2.1. Works like a charm :D
[Xposed General] Lim_Dul:
Oh, by the way, I fixed my previous problem of the Xposed Framework Systemless not being identified by the Installer by... running the uninstall script? Now it's properly detected. Very weird.
[Xposed General] VaThInK:
Anyone managed to get OTA update to work in the end? I have followed the instructions on the first page and have systemless root and xposed working fine. Got notified that there is a 375MB OTA. Proceeded with the update. My Note 4 rebooted into TWRP and does nothing. I then manually rebooted my phone back to system and got prompted with OTA update fail popup.

Edit: TWRP actually did try to install the update but fail with the following error message.

Updater process ended with ERROR:7

Error installing zip file '@/cache/recovery/block.map'

I have also tried flashing stock recovery back. This time it tried to install OTA update in recovery and then rebooted automatically but the update didn't install through and I'm still prompted with OTA update fail popup. Any advice? Have I missed anything?

Thank you in advance.
[Xposed General] Artim_96:
Same problem here, Note 4 too.

When you disable XPosed first the updater sees that the device is modified and doesn't search for updates. If you leave it enabled, the downloaded zip files seems to be always corrupted.
[Xposed General] Illuminatus_:
Can someone please upload previus version v86.1 because this one isnt working for me. When i flash v86.2 i got error 1

Thank you.
[Xposed General] vital21:
HI guys,

131 pages...hooh...too much to read. Could someone please confirm if sysless xposed + sysless SU pass the safetyNet check? Or it's not possible at this moment?

I will appreciate your advice!

Cheers! ;)
[Xposed General] Captain_Throwback:
How about you just read the first post?
[Xposed General] vital21:
I do, few times...really!

As I understand that SafetyNet detect even sysless Xposed...and as a result there is a work around -> "Switch off Xposed, Reboot and Android Pay should work".

But i cant get the sense of this workaround.

If Xposed will be switched off, all custom modules gonna stop working aswell, correct me if wrong..

This fact confused me a bit...thats why I ask for short advise to make it clear...

Cheers ;)
[Xposed General] Citizen_Snips:
You've answered your own question. If you want to use Android Pay you need to disable Xposed and reboot and live without your modules for 30 seconds.
[Xposed General] k_l_o:
Just to add, from my weeks of frustration with Android Pay and Xposed, you'll need to do a HARD REBOOT, not a Soft/Hot reboot. It won't work if you just Soft/Hot reboot. Took me forever to realize this due to my stubbornness.
[Xposed General] Serenei:
do i have to restore boot / system image and flash superSu again after i install the Material design Xposed installer? i dont want to wipe data again..

Im already rooted - flashed 2.74-2 with ForceEncrypt for HTC 10 from here, then updated to 2.76 from SuperSu, does it qualifiy as the 2.76 required for the systemless Xposed?

http://xdaforums.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258

Then i tried to install the systemless Framework and im getting "Xposed Version vXXX (Systemless by topjohnwu) is installed but not active".

Log: Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (No such file or directory)

do i have no choice but to install the official Xposed? is it even possible on systemless root? i do want to have to option to take OTA when the day comes...
[Xposed General] curioct:
Is there any chance of a build for lollipop 5.0 sdk21

or does any one know where I can find a later normal xposed in v86 [update] think I found this deep in another won't be able to test until son is back next week
[Xposed General] teddy0209:
You have to flash supersu2.76 via recovery...
[Xposed General] Artim_96:
You might want to install SuperSU 2.76 through FlashFire, that seems to have the same effect like restoring boot and flashing it.

Afterwards look in SuperSU settings under the point "install to /system" it should be greyed out and say that it's installed as systemless
[Xposed General] Serenei:
alright , it seems flashing 2.76 over the modified older version doesn't temper with the flags, appears to be working now, Thanks.
[Xposed General] ghbuur:
is there a chance to get an xposed for x86_64 device? seems it should be possible...

https://gist.github.com/shakalaca/86ac06a6be14a6d9331b
[Xposed General] moriel5:
This is not the official Xposed thread, this is the unofficial systemless Xposed thread.
[Xposed General] FPSUsername:
It would be nice if xposed will evolve with enable/disable on the fly without rebooting, but that would bug the phone a lot if you use customizability modules such as gravity box
[Xposed General] Artim_96:
That would be too great to be true. It will already be a big step when in N you doing need any recompiling after installation/update. At least that's what I read from the changes already known
[Xposed General] kryptikal:
Hi,

I'm using Pure Nexus Rom (7/9 build w/ AOSP dialer) on Nexus 6 with systemless SuperSU 2.76 and systemless Xposed 86.2

When I toggle xposed to OFF and reboot (to use Android Pay) Visual voicemail disappears from the dialer app. I can re-enable it and it works fine until I toggle xposed back to ON and reboot. Upon rebooting, Visual voicemail is gone again... go into the dialer > calls > voicemail, toggle visual voicemail a couple times and it reappears in the main screen of the dialer.

Wondering if anyone else has noticed, or can confirm, the same issue?
[Xposed General] waylo:
I've read some reports on the Nexus threads that the Safetynet API has been altered/fixed, maybe just today, so it is now able to detect root on systemless-root devices, thus disabling Android Pay completely, regardless of systemless-xposed status.

Any confirmation from the users here?
[Xposed General] Citizen_Snips:
Just disabled Xposed and rebooted. SafetyNet failed. No changes since the last time I did that and it passed. Gonna try a clean install of everything again and see. I'll report back.

Edit: Still failed... :/
[Xposed General] Artim_96:
Oh great...

But wasn't it already finding it earlier? For all I remember, shortly after Chainfire made the systemless root, he stated that Google changed something and detected systemless root. What did even changed, that it wasn't detected anymore till now?

But hey, hopefully he will find a way to trick Google another time. I don't know how he's still involved since he gave it to a company, but maybe it won't take long to fix that...
[Xposed General] Max88888:
Confirm that systemless root triggers SNET

It just started from today...
[Xposed General] Revil:
How fix Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log

On my OnePlus 3 with stock ROM I got following error after installing systemless version:

Log: Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (No such file or directory)

Instructions to fix it are simple:

Disable

Immediate soft reboot

Enable (should re-create file)

Immediate soft reboot

Done

Enjoy
[Xposed General] darthkir:
Hi. I have tested this multiple time with clean flash. I am convinced that with Xposed, I am experiencing battery drain. Before Xposed, my SOT is around 7 hours. With Xposed, my Sot is only around 5 hours. I only have GravityBox installed.
[Xposed General] Portgas D. Ace:
Did you compare your regular SOT (7 hrs) to only Xposed installed (without Gravity Box enabled)? There is quite a high chance that GB is causing the drain.
[Xposed General] darthkir:
I am about to do that now. My previous test was with Xposed + GB on my ROM before and after clean flash, and without Xposed + GB.

The only thing I need from GB is the ability to reconfigure the nav bar. I need the ability to rearrange the position and configure each button individually for features like switch to previous app and kill app. Any alternatives to GB?
[Xposed General] Portgas D. Ace:
Well, most custom ROMs do have such kind of re-arrangement implemented by default nowadays. If your current one doesn't suport it, you can either search for another ROM that does support this or search for alternatives to GB. I know that there is one, but I am currently missing the name of this module. Search for "Xposed Nav (or Navigation) Bar", this should bring up something.
[Xposed General] darthkir:
Unfortunately, P9 is currently lacking in that department. However, thanks for the suggestion and I will certainly do so.
[Xposed General] ShapeShifter499:
I can confirm it works here if I remove Systemless Xposed.

So it's either Systemless Root and Android Pay OR Systemless Root and Systemless Xposed without Android Pay.
[Xposed General] Citizen_Snips:
As mentioned earlier, it was the same before systemless anything came out. A few users were affected at first, then it rolled out to everyone and stopped working entirely. My exact setup was working 2-3 days ago, now disabling both systemless Xposed and root still gives me a SafetyNet fail. I wouldn't imagine yours will pass much longer. There's scattered reports of the same from others all over XDA at the moment.
[Xposed General] Artim_96:
What kind of device/system do you have? I don't know how the API gets its updates, through system updates or through Google Play services.
[Xposed General] ShapeShifter499:
Say it isn't so!

---------- Post added at 07:23 AM ---------- Previous post was at 07:16 AM ----------

I was running TruPureXMM 2.9 stock based ROM, for the Moto X Pure. My Moto X Pure has the model XT1575 Clark.

http://xdaforums.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155

HOWEVER! I checked the SafetyNet helper app again and it's now failing.

---------- Post added at 08:01 AM ---------- Previous post was at 07:26 AM ----------

So no more Android Pay with Root it seems? If so I'll go ahead and install CyanogenMod on my phone as the only reason I kept stock was for Android Pay.
[Xposed General] osman34:
Did Any of u guyz got any issues with facebook apps on my phone it crashes after flashing xposed
[Xposed General] moriel5:
I don't use Facebook, but those who it happened to them say that you need to uninstall and reinstall Facebook.
[Xposed General] osman34:
ok i hope that works thnx
[Xposed General] Artim_96:
At least not for the moment, no. If there is a way to reenable it, it will take some time to find it
[Xposed General] mobileman88:
Does it mean that I need to not just remove Xposed but all the xPosed modules for Systemless Root and Android Pay to work or just uninstalling xposed will do? Main reason I am using Xposed is for GravityBox and BootManager
[Xposed General] Citizen_Snips:
As it stands now, you need to disable systemless Xposed as well as fully unrooting systemless root. I tried just disabling it and it still won't work. Device can't be rooted with AP since all this started.
[Xposed General] LuanTeles:
its always says that is installed but not active
[Xposed General] mobileman88:
That's not enough. I tried. I disabled both systemless xposed and supersu. doing a full unroot if it works. It's doing the "optimizing apps " thing now. Seems I have 30 less apps to optimize compared to when I installed xposed. I only disabled xposed and unrooted but did not uninstall xposed. Not sure if it will works. This probably puts the end to my use of Android Pay. Switching to and from AP will take 30 mins each time. Not worth it.
[Xposed General] RandomPooka:
Guys, there's always the up side to systemless root and xposed being that you no longer have countless people posting about errors during flash that are easily solved by deleting some of the unused system bloat (language support, typically)

That alone makes me glad that this exists. I'm not running a ROM that requires me to delete anything, but if I were on stock? I'd be all over systemless root/exposed
[Xposed General] mobileman88:
Indeed and it's much cleaner to remove certainly.
[Xposed General] Killadelphia:
看不懂英文，我應該如何更新?? 我是6.0的系統，32位元的cpu
[Xposed General] Portgas D. Ace:
No English language = no help.
[Xposed General] moriel5:
That's not just non-English, that's not even based upon Latin.

Otherwise I would have been able to see the characters.

XDA Labs.
[Xposed General] Lucas Eugene:
Guys do you know if this works with NOTE 5 (N9208) with Android 6.0?
[Xposed General] grep_i:
Exactly that's why I only buy Nexus devices.

Easy to unlock bootloader, highly tweakable and just stock Android is enough and little to none bloatware.
[Xposed General] Artim_96:
尝试使用谷歌晶体管或相似！ 也许尝试写中国的版本太多，所以如果翻译的不清楚，我们可以使用它。

As long as you don't say what device you use we can't tell you how to update it since these things are device specific. Or just search for a ROM for your device that is a Marshmallow/6.0 built if there are any
[Xposed General] DirkStorck:
What? Please in English. Thanks ☺️

Gesendet von meinem SM-G900F mit Tapatalk
[Xposed General] Artim_96:
I already told him (with the help of Google translate) that he should use Google translate or similar and that he can include the Chinese version here for the case the translation is not clear
[Xposed General] natan:
Hello. I had 85.7 installed and then I flashed 86.2 zip from Post 1. When I open Xposed Installed I still see Green Checkmark with a message "Xposed Framework version 85.7 (Systemless by topjohnwu) is active. " Screenshot attached.

Should it not say 86.2 ? I installed in Recovery and installation was a success.

I also believe there's been some battery drain after the installation where there was none on 85.7. I am on S7 Edge Renovate ROM.

Thanks!
[Xposed General] grep_i:
I guess you didn't flash the Xposed uninstaller prior to flashing v 86.2.
[Xposed General] natan:
Thank you. Correct. I did not flash Xposed uninstaller. I did not know I need to do that before upgrading the xposed framework.. This step is not mentioned in the Installation Instructions. I will try that.
[Xposed General] Artim_96:
Well, I would say you didn't even restored your boot.img. because of you did that XPosed 85.x wouldn't be able to load. The uninstaller is just to get rid of the now unnecessary files
[Xposed General] natan:
I just flashed the Uninstaller, rebooted, flashed 86.2==>Xposed Installer still says i'm on 85.7. All flashing was done in Recovery..

Any steps i'm doing incorrect?

I also tried flashing the uninstaller and then checking Xposed Installer status and it STILL said i'm on 85.7 . Is there anything else required for UNinstallation besides flashing the uninstaller zip file?
[Xposed General] Artim_96:
Follow the guide in the OP! If you can't even do that you shouldn't even use XPosed!

Stock users: Restore your boot image back to stock. If you have old Xposed installed on your system, please also restore system image back to stock, or use the uninstaller in OP to remove them.
[Xposed General] Citizen_Snips:
Use a file explorer with root access and navigate to /data/ and delete Xposed.img. Reboot and it should tell you that Xposed isn't installed. You can reboot to recovery and flash the uninstaller again and then flash the newest zip and you should be good to go.
[Xposed General] Artim_96:
He should still restore his boot.img at first, that's not for no reason the first point in the guide and topjohnwu already mentioned why
[Xposed General] natan:
Thanks. Missed that step. Will try.

P.S. no need for judgments here. Not helpful :)
[Xposed General] grep_i:
It is mentioned see next quote I marked it blue for you:
[Xposed General] Bajanman:
I was having the same problems as you having now. The uninstaller didn't help me either after rebooting the older version was still installed. And I tried it like 10 times with the same results. What actually got it working was following another users steps, which I didn't think would work but it did.

What got mine working:

restore original boot.img done

reboot

flash supersu 2.76 (no reboot)

flash xposed systemless (no reboot)

flash kernell reboot done.

You should get Android is updating screen.
[Xposed General] Bajanman:
My question can someone disable Xposed and please check the safety net app to see if you get a pass result. I'm getting this below after switching mine off...

http://cloud.tapatalk.com/s/57994184acfc5/Point Blur_Jul272016_123802.jpghttp://cloud.tapatalk.com/s/5799415bc4eff/Screenshot_2016-07-27-12-38-35.jpghttp://cloud.tapatalk.com/s/5799419f46781/Screenshot_2016-07-27-12-42-37.jpg

Thanks,

Bajanman
[Xposed General] garthybarthy:
It doesn't work anymore passing safety net, Google changed something and now it fails with xposed disabled even.
[Xposed General] Bajanman:
Thanks for the quick reply, haven't checked it since I updated to the latest version. So that means we can't disable to use Android pay. ?
[Xposed General] garthybarthy:
Nope, not until some clever person finds out what the problem is and even then it depends if there's a solution.
[Xposed General] topjohnwu:
Android Pay will not work with systemless root at all in the current state.

BTW, I'm working on a BIG project, might be able to give a permanent workaround that is unpatchable.

Teaser is that I can fix SuperSU not running reliably, also add support for more devices and more mods, not limited to Xposed.

Will release soon :D
[Xposed General] teddy0209:
That's a very good news!!! ?
[Xposed General] mielletseed:
Strange, with flashing kernel as last part yoz should revert the changes of SuperSU and systemless XPosed
[Xposed General] natan:
Thank you. I did miss this point "Custom rom users: Re-flash your rom to get a fresh start"
[Xposed General] grep_i:
No you can't pass the safety net with Xposed disabled.

Already told in another post you must remove systemless Xposed and systemless root to pass safety net.

I see it's already answered by others to again.
[Xposed General] eraser0:
The only problem i have faced is gravity box pie control,

Enabling the pie control won't allow me to edit the permissions in apps settings given the message of SCREEN OVERLAY DETECTED

Moreover it will reset the applications permission after every boot