Database Develop

[Q] Xposed Framework Install Issue

Hello anybody that may be able to help me,
I recently decided to update the xposed framework on my HTC One (running Android Revolution HD 53.0). When i clicked install it decided to reboot my phone, without actually updating the framework and this happened every time i clicked install. I even changed the Installation Mode and have tried all 3, none of them worked. So i uninstalled the frame work to see if i could reinstall it and it kind of worked, the XposedBridge.jar got installed but the app_process hasn't.
Any idea how i can get this to install?
Thanks for any help that you can possibly give me.

destruck51 said:
Hello anybody that may be able to help me,
I recently decided to update the xposed framework on my HTC One (running Android Revolution HD 53.0). When i clicked install it decided to reboot my phone, without actually updating the framework and this happened every time i clicked install. I even changed the Installation Mode and have tried all 3, none of them worked. So i uninstalled the frame work to see if i could reinstall it and it kind of worked, the XposedBridge.jar got installed but the app_process hasn't.
Any idea how i can get this to install?
Thanks for any help that you can possibly give me.
Click to expand...
Click to collapse
I have the same problem too every time I update to new version it will not update our install properly. I'm using a HTC one m8 with maximus 3.0 rom. I tried uninstall and install the xposed framework using classic write to system and zip recovery flash. Both doesn't work. It says failed. Very frustrating. For version2.6 I managed to get it workingby manual installing thefile from repository but version 2.61 61 fit some reason just won't work.

When trying to use the recovery install method, how is it failing? Is the zip being copied correctly but the flash (after rebooting to the recovery) falling? If so, what's the exact error?
If the copying is what's failing, then post a logcat.

Any help please? Running kitkat omega for the note 2 N7100
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-N7100 using Tapatalk

pani690 said:
Any help please? Running kitkat omega for the note 2 N7100
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
You can give this a try, but you'll need to provide a logcat for more info.

I tried the fix but still the same issue. The folder seems to be empty.
Sent from my GT-N7100 using Tapatalk

pani690 said:
I tried the fix but still the same issue. The folder seems to be empty.
Click to expand...
Click to collapse
Do the second part of my reply, then:
you'll need to provide a logcat for more info.
Click to expand...
Click to collapse

I'm in the same boat. Should I open a new thread or keep it all in here? Even trying manually, no files are put on the sd card and no "files" folder is created.
Sadly, I don't even have a log file. XPosed says it can't find it, and the log folder is empty.

schnp said:
I'm in the same boat. Should I open a new thread or keep it all in here? Even trying manually, no files are put on the sd card and no "files" folder is created.
Sadly, I don't even have a log file. XPosed says it can't find it, and the log folder is empty.
Click to expand...
Click to collapse
If it's the exact same problem, here is fine. Follow this tutorial to get a logcat.

GermainZ said:
If it's the exact same problem, here is fine. Follow this tutorial to get a logcat.
Click to expand...
Click to collapse
Okay, boss, here's the logcat. Odd thing I noticed is that there's no /files/ folder under /data/de.robv.android.xposed.installer/ which indicates that nothing is being downloaded when I choose any of the install methods.

schnp said:
Okay, boss, here's the logcat.
Click to expand...
Click to collapse
Did you press "Install/Update" after opening the Xposed Installer? Basically, do this:
Clear the logcat if you know how;
Start recording the logcat;
Open the Xposed Installer;
Tap "Framework" followed by the "Install/Update" button;
Stop recording the logcat and upload it.
schnp said:
Odd thing I noticed is that there's no /files/ folder under /data/de.robv.android.xposed.installer/ which indicates that nothing is being downloaded when I choose any of the install methods.
Click to expand...
Click to collapse
Nothing is downloaded - only extracted.

So I have the exact same issue. I downloaded the 2.6.1 today and it would not install/update. Whenever I would do it super user would prompt me and when I granted it the phone would immediately reboot. I have the HTC One and I haven't found anything to fix this. Is there anyway to even get a working older version? I would really love some answers for this problem. Thanks !

GermainZ said:
Did you press "Install/Update" after opening the Xposed Installer? Basically, do this:
Clear the logcat if you know how;
Start recording the logcat;
Open the Xposed Installer;
Tap "Framework" followed by the "Install/Update" button;
Stop recording the logcat and upload it.
Okay, new attempt of the logcat. Logcat cleared, recorded, ran as a classic install. The phone immediately went black and rebooted so the very last bits should be the ones pertinent to the crash.
Click to expand...
Click to collapse

∆Ace∆ said:
Whenever I would do it super user would prompt me and when I granted it the phone would immediately reboot. I have the HTC One and I haven't found anything to fix this.
Click to expand...
Click to collapse
schnp said:
The phone immediately went black and rebooted so the very last bits should be the ones pertinent to the crash.
Click to expand...
Click to collapse
That sounds like a very strict protection of the vendor which prevents writing to /system by simply restarting when something tries to do so.
What you can try in Xposed Installer itself is installation via recovery, the protection might not be active there.
Without any guaranty, this is what I found from quickly googling: http://forum.xda-developers.com/showthread.php?t=2701816
Make sure you read about it carefully before trying anything, I can't provide any more assistence about it.

I got the same issue with Nexus 5 running Android L, CWG. Here is a screenshot.

New to Rooting
I am having an issue when trying to re-install xposed on my Galaxy s4. I just rooted my phone this morning and had this installed once, and before i really knew how to use it or what it did I uninstalled it. Now when I go to re-install any APK it looks like it is going to install but then all i get is "xApp Not Installed".
Please Help I would really like to get this installed again so that I can start messing around with it.

thepurplbanana said:
I got the same issue with Nexus 5 running Android L, CWG. Here is a screenshot.
Click to expand...
Click to collapse
Have the same issue on my S4. But on SDK 19. What could be causing this? any possible solutions? I only had this problem when i decided to clean install my rom again. with the same framework i used before.

Hello. I have a problem with my n910f snapdragon note 4. When i use spen an infinite ringtone start play and i cant stop it without restart. I read thas is xpose problem. Can anyone direct me find a solution. Thanks in advance!
Sent from my SM-N910F using Tapatalk 2
Sent from my SM-N910F using Tapatalk 2

I have problem with my xposed installerinstaller. Im using RR rom for note 3 and its not working… it says its not available yet for it. Is there aby other way for it to be fixed?

Do i need custom recovery to install xposed?

Android Pay

Android pay doesn't seem to work with my bootloader unlocked rooted MotoX14. Is this a result of the root? Kinda bummed, has anyone else tried it?
Edit: disregard I fixed it. Simply uncheck "Enable Superuser" in the supersu app - Then verify your cards then recheck the "Enable Superuser" - Profit (err spend money)

I tried this, but I'm still getting a message that Google cannot verify that my device or the software running on it are Android compatible. Was this the same issue that you encountered? Are you running a custom ROM, and if so, which one? I'm on the latest Nexus Experience.

Guys you have to be on pure edition, and non rooted devices.
Sent from my XT1095 using XDA Free mobile app

Yes I was able to get my cards verified but when I tried to checkout it gave me an error at the register. I will try again at a different store, but it appears that the service does not like to play well with root/unlocked phones. I am on the stock Moto X lollipop 5.1 software, no ROM. I think ROMs are more temperamental in reference to Android Pay.
Thought, would turning off superuser through the SuperSU affect daily activities? I used root mainly to get tethering as well as some system modifications like volume panels and such. Would turning root off cause those to not work or only services that routinely need to access root (ie: Greenify)

I am having the same issue. Tried disabling superuser but get the same error. Also tried the xposed module No Device Check, didn't work.
Unlocked bootloader, stock rooted rom and xposed.
Need a way to get around this.

Same problem here. Stock Rom 4.4, super User disabled,no luck.

I'm having the same issue with the stock 5.0 rom, with unlocked bootloader, supersu disabled, twrp recovery, and xposed.
I've tried with rootcloak and no device check xposed modules too.
From what I've gathered reading other threads android pay doesnt like custom roms so I'm wondering if it's the changes that xposed makes that's causing issues or if it could be the custom recovery. Many people are having success just unrooting but that didn't work for me so there's more that's being flagged as not compatible in my setup. I've seen people saying they have no issues with unlocked bootloaders as well so really thinking it's recovery or xposed. I just don't use tap and pay enough to try wiping the phone and playing with settings though.

Same problem here. . . XT1095, stock 5.1, rooted, no XPosed. . . disabled SuperSU, rebooted, re-loaded credit card, same error. I even tried "permanently removing root". Same error.
Too bad. . . I've been geeking out since 2012 paying for items using Google Pay and NFC. . . guess I have to revert to the swipe

WOP_Drive said:
Same problem here. . . XT1095, stock 5.1, rooted, no XPosed. . . disabled SuperSU, rebooted, re-loaded credit card, same error. I even tried "permanently removing root". Same error.
Too bad. . . I've been geeking out since 2012 paying for items using Google Pay and NFC. . . guess I have to revert to the swipe
Click to expand...
Click to collapse
Did you reboot your phone after you disabled SuperSU? It worked for me and I had xposed installed

Yes.... I did reboot after disabling SuperSU.

I tried rebooting after disabling superuser and it still didn't work, I wonder if TWRP is causing the issue.

Never got it to work by disabling SuperSU. I even restored an old unrooted backup, but still no luck. However, I'm sure it's not TWRP. I loaded up a clean image, still using TWRP, and Android Pay worked. Go figure. Not sure what was wrong with my unrooted backup, but I can confirm Android Pay works when unlocked and on TWRP recovery.

Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

GatorsUF said:
Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
Click to expand...
Click to collapse
Mine does not show modified, doesn't show that box at all actually.
I'm on 5.0 though, was that added to 5.1?

I am on 5.1, guess it's a new addition.

Has anyone tried re-locking the bootloader and then try getting Android Pay to work? I haven't yet. Here's an article that walks you through it using a Nexus device (not sure if it'll work on my XT1095).
article/video
I'm running stock 5.1 on a rooted XT1095 (bootloader unlocked) with TWRP. If anyone has step-by-step instructions that'll get Android Pay to work on this configuration, I'm "all ears"! THX!

Relocking the bootloader does not affect it.
Sent from my XT1095 using Tapatalk

I'm on 5.1 on an XT1095. I ended up restoring that stock OTB system image I mentioned over the non-rooted Nandroid backup I had. Works fine now. Still unlocked. Still using TWRP. I don't see that software status message under about phone though. Weird.
Sent from my XT1095 using Tapatalk

GatorsUF said:
Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
Click to expand...
Click to collapse
I'm on 5.1 pure edition, mine doesn't have "modified"

ksd316 said:
I'm on 5.1 pure edition, mine doesn't have "modified"
Click to expand...
Click to collapse
Does android pay work on you phone?

SafetyNet CTS profile match false

This thread is dedicated to understanding what is causing the SafetyNet to report the CTS profile match as false.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried unrooting and flashing a new kernel, but the error remains.
Anyone knows what does it check?
@Tesla
@xstahsie

What I can tell you, Busybox is not the problem in my case. Fully unrooted und un-busyboxed my Note3 (see sig) by modding the ROM I use pre-flash, wiped /system and put it on there with TWRP. Nope. I am close to think that there's some thing custom ROMs pass to Google by SafetyNet and are being detected as not official by that. The fingerprint (In my case "samsung/hero2ltexx/hero2lte:6.0.1/MMB29K/G935FXXU1APEK:user/release-keys") compared to H/W maybe...

I have the same problem with a unroot cyanogenmod 13. Pokemon Go die.

sakis_the_fraud said:
This thread is dedicated to understanding what is causing the SafetyNet to report the CTS profile match as false.
View attachment 3902690
I tried unrooting and flashing a new kernel, but the error remains.
Anyone knows what does it check?
@Tesla
@xstahsie
Click to expand...
Click to collapse
Assuming you have made a NANDROID backup via TWRP when the phone was unrooted, simply restore "boot" from your backup. If you don't have a copy, you'll need to reflash your ROM. And if you have to do that, just flash boot and system.
Sent from my Nexus 6P using Tapatalk

I'm on the same boat as you guys. Exact same error, CM13 with su removed, nothing else modified. No idea why CTS is now false.

xstahsie said:
Assuming you have made a NANDROID backup via TWRP when the phone was unrooted, simply restore "boot" from your backup. If you don't have a copy, you'll need to reflash your ROM. And if you have to do that, just flash boot and system.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Phone was rooted on second boot.
I will try to flash a stock kernel when i return home, but i don't expect much.
Flashing stock system is definitely not an option, do you think dirtyflash will work?
Sent from my Xperia Z5 using Tapatalk

sakis_the_fraud said:
Phone was rooted on second boot.
I will try to flash a stock kernel when i return home, but i don't expect much.
Flashing stock system is definitely not an option, do you think dirtyflash will work?
Sent from my Xperia Z5 using Tapatalk
Click to expand...
Click to collapse
I've dirty flash system on LG G3 many times without any issues. Just wipe cache afterward.
Sent from my Nexus 6P using Tapatalk

@AbiDez , @Boosik , @asdone001 check here, we all have the same problem!
anyone here tried switching SELinux mode as phhuson suggested?
phhusson said:
For people for which SafetyNet fails, is /sys/fs/selinux/enforce or policy readable by an application?
On standard Android it's not readable, but perhaps that's the difference on your devices.
Click to expand...
Click to collapse
here is a guide:
koron393 said:
Code:
$ getenforce
This prints SELinux mode. (Permissive or Enforcing)
Code:
$ su
# setenforce 1
This will set SELinux mode Enforcing.
or try
Code:
# setenforce Enforcing
Click to expand...
Click to collapse
my kernel is set to permissive and I can't switch it, i will try to flash stock and report back.

sakis_the_fraud said:
@AbiDez , @Boosik , @asdone001 check here, we all have the same problem!
anyone here tried switching SELinux mode as phhuson suggested?
my kernel is set to permissive and I can't switch it, i will try to flash stock and report back.
Click to expand...
Click to collapse
Already tried it, but not with those commands. I switched from an unofficial CM13 ROM with SElinux set to permissive to an official CM13 nightly with SElinux set to enforcing. I removed root and bam, Safety Net check passes all checks now.

@sakis_the_fraud
My kernel is
.
On pure stock rom with stock recovery without root - SafetyNet is all green, PoGo works.
On stock rom with TWRP without root - SafetyNet is all green, PoGo works.
On stock rom with TWRP and superuser-r266-hidesu - SafetyNet is red (CTS profile match: false), PoGo doesn't work.
My superuser-r266-hidesu config is "eng noverity crypt hidesu".
But as phh asked "/sys/fs/selinux/enforce" is readable on my device, I can open it in SE File Explorer (contains 1). "/sys/fs/selinux/policy" gives me access denied.
---------- Post added at 01:38 PM ---------- Previous post was at 12:39 PM ----------
Fixed it by setting my superuser-r266-hidesu to verity (was using noverity to be able to mount /system as rw).

Boosik said:
My superuser-r266-hidesu config is "eng noverity crypt hidesu".
Fixed it by setting my superuser-r266-hidesu to verity (was using noverity to be able to mount /system as rw).
Click to expand...
Click to collapse
great info, we are getting somewhere. :good:
could you tell me how to change this setting?
Also, you could try with "noverity setting" to use the "root switch" from shakalaca.
You can find the latest version here at post no: 263.

sakis_the_fraud said:
great info, we are getting somewhere. :good:
could you tell me how to change this setting?
Also, you could try with "noverity setting" to use the "root switch" from shakalaca.
You can find the latest version here at post no: 263.
Click to expand...
Click to collapse
Open the superuser-r266-hidesu.zip archive and there is config.txt file. Open it and there are some words "eng verity crypt hidesu" I had it set to "noverity" it has to be "verity". Also root switch app doesn't seem to work with phh's superuser.

Boosik said:
Open the superuser-r266-hidesu.zip archive and there is config.txt file. Open it and there are some words "eng verity crypt hidesu" I had it set to "noverity" it has to be "verity". Also root switch app doesn't seem to work with phh's superuser.
Click to expand...
Click to collapse
thanks!
I see that the default option is verity, but it isn't passing the CTS profile match for me.
have you tried with chainfire's root and hidesu, maybe got some luck with that!

sakis_the_fraud said:
thanks!
I see that the default option is verity, but it isn't passing the CTS profile match for me.
have you tried with chainfire's root and hidesu, maybe got some luck with that!
Click to expand...
Click to collapse
Unfortunately chainfires su 2.78-SR1 has huge performance hit on my phone for some reason and makes it nearly unusable, so that is no option for me.
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Are you using Magisk?
I do not use it.
I have stock rom and flashed superuser-r266-hidesu.zip nothing else. Everything works fine now.

Boosik said:
Unfortunately chainfires su 2.78-SR1 has huge performance hit on my phone for some reason and makes it nearly unusable, so that is no option for me.
Click to expand...
Click to collapse
i haven't tried it yet, reading about systemless install and the rest procedure.
what device are you using?
Boosik said:
Are you using Magisk?
I do not use it.
I have stock rom and flashed superuser-r266-hidesu.zip nothing else. Everything works fine now.
Click to expand...
Click to collapse
no.
here are the setups I have tried

sakis_the_fraud said:
i haven't tried it yet, reading about systemless install and the rest procedure.
what device are you using?
no.
here are the setups I have tried
View attachment 3903539
Click to expand...
Click to collapse
My device is Huawei Mate 8 (NXT-L29C432)
AFAIK "dm verity" has to be on for CTS to pass.
---------- Post added at 02:39 PM ---------- Previous post was at 02:35 PM ----------
Is your current phone Sony Z5?
On the Magisk page, there is something about Sony kernels being unpatchable, maybe that is the problem why your phone does not boot while trying it with dm verity on?
Sony devices generally: Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds, if you know any addition quirks about Sony boot image modifications, please contact me
Click to expand...
Click to collapse

Boosik said:
AFAIK "dm verity" has to be on for CTS to pass.
Click to expand...
Click to collapse
If yes, I'm screwed! I have no clue why it doesn't boot with that on!
Boosik said:
Is your current phone Sony Z5?
On the Magisk page, there is something about Sony kernels being unpatchable, maybe that is the problem why your phone does not boot while trying it with dm verity on?
Click to expand...
Click to collapse
yes, but there is a tool that can patch the kernel and edit those kind of things such as dm verity, sony ric, root, twrp etc.
also, magisk was working fine on my phone, i was using it before turning to phh's v266.

What does it mean if its says this and my phone is still vanilla.as in never been rooted or used thirdparty apps or that sort of stuff
Sent from my Elite 5 using Tapatalk

javaxcore said:
What does it mean if its says this and my phone is still vanilla.as in never been rooted or used thirdparty apps or that sort of stuff
Click to expand...
Click to collapse
something is tipping cts, we are searching to find it.

@Jayster06 check here
Something is tripping CTS, if it was on /system, why it isn't reported with stock kernel?
If you are rooted, the checker reports that the response validation failed, so it's not the root.
here are the configurations I have tried so far...
please report back if you found a solution.

Bootloop after installing Xposed via Magisk

I've got the Google Fi variant of the Moto X4 (XT1900-1). It's running stock build OPW28.46-18 (Android 8.1). TWRP 3.2.1-1. I was able to install the latest Magisk no problem and I have working root access. My issue arises when I try to install the Magisk variant of Xposed Framework. When I do this and reboot, the phone seemingly gets caught in a bootloop. I've let it sit for 15-20 minutes to see if it would recover and it does not. To exit the loop, I reboot to fastboot then to TWRP and flash a ZIP that allows me to uninstall Magisk modules right from TWRP. Reboot and phone works fine.
I've tried both versions of the Xposed Framework in the Magisk downloads section (the smart version that automatically chooses the proper framework, and the explicit SDK 27 version), as well as downloaded the ZIP and tried to install it from TWRP. Similar result in all cases. I have only tried the "systemless" Xposed that works with Magisk thus far.
Has anyone else run into and dealt with this issue, or have any suggestions? I'd really like to get Xposed working so I can get XPrivacyLua going and switch over to using this phone as my daily driver.

how are you flashing Xposed? from Recovery or magisk?

abhi212b said:
how are you flashing Xposed? from Recovery or magisk?
Click to expand...
Click to collapse
I've tried both: installing via Magisk Manager as well as flashing zip in TWRP (xposed-v90.2-sdk27-beta3-topjohnwu.zip). Similar results in both cases.

I didn't think there was a version of xposed compatible with Oreo yet but I could be wrong. This would be a better question in Xposed Section of XDA.

Neffy27 said:
I didn't think there was a version of xposed compatible with Oreo yet but I could be wrong. This would be a better question in Xposed Section of XDA.
Click to expand...
Click to collapse
There's been a beta version for Oreo 8.0/8.1 since maybe January (t's on beta version 3 now I think). I'd tried it on my OnePlus 3 with success. I thought maybe it was a Moto X4 issue and I might as well check here first to see if anyone else with this phone had already run into this and fixed it. I'll go ahead and ask the question in the Xposed section of the forum. Thanks!

Seems the OP of this thread has Xposed working: https://forum.xda-developers.com/moto-x4/help/oreo-magisk-xposed-modules-reboot-t3745612 - Maybe they could help.

Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Thanks for posting that

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Thanks for the info! Perhaps it's an incompatibility with the stock ROM then, as that's what I'm using. I haven't flashed a different ROM nor GApps on this phone yet (mostly out of fear of not being able to go back to stock with seemingly no official factory images floating around).

I got bootloops too with Magisk and systemless Xposed. I had pattern password set, so I couldn't get TWRP full access to the data to remove Xposed, so I had to delete all my data.
From what I read, Magisk and systemless xposed will not pass SafetyNet so Android pay won't work.

dcdruck1117 said:
Thanks for the info! Perhaps it's an incompatibility with the stock ROM then, as that's what I'm using. I haven't flashed a different ROM nor GApps on this phone yet (mostly out of fear of not being able to go back to stock with seemingly no official factory images floating around).
Click to expand...
Click to collapse
No.. The stock rom is compatible! I simply flashed magisk and then xposed v90... The latest ones! Yeah safety net is broken! But there is a workaround! It is disable the xposed module from magisk and reboot.. Nd then you can use android pay... Once you are done! Activate the module.. And reboot!

solara1973 said:
I got bootloops too with Magisk and systemless Xposed. I had pattern password set, so I couldn't get TWRP full access to the data to remove Xposed, so I had to delete all my data.
From what I read, Magisk and systemless xposed will not pass SafetyNet so Android pay won't work.
Click to expand...
Click to collapse
Thanks for the info. You're correct about SafetyNet and Android Pay; I gave up on Android Pay years ago for that reason, because Xposed is too important to me to give it up. Perhaps I'll try starting from scratch again with this phone. I'm hesitant to flash ROMs on this phone, stock or otherwise, because of the scarcity of factory images available should something go terribly wrong..
abhi212b said:
No.. The stock rom is compatible! I simply flashed magisk and then xposed v90... The latest ones! Yeah safety net is broken! But there is a workaround! It is disable the xposed module from magisk and reboot.. Nd then you can use android pay... Once you are done! Activate the module.. And reboot!
Click to expand...
Click to collapse
Thank you. I think I'll try to start over and see if I can get it to work. Or maybe I will try using the regular version of Xposed (not the Magisk version).
If you know of a repository of factory images for the Android One version, that would be helpful. I'm finding some images for the retail version but not much love for the A1 version.
Edit: I just found this post which seems like it may contain what I'm looking for, "Latest Project Fi Firmware (Android 8.1)": https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

I flashed back to stock using the files from the link in my previous post. The weird thing there is that SafetyNet fails immediately now, clearly some side effect of flashing back the stock images. Anyway, I again installed TWRP, then Magisk, then Xposed, and again ran into the same boot loop. I don't know what else to try other than to wait for maybe a new Xposed beta, or maybe try an even older Oreo build on this phone and see how that works.
I've run Xposed (and more recently, Magisk+Xposed) on every Android device I've owned since Xposed has been in existence, and this is the first phone to ever give me trouble.

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Which Stock ROM version are you using? Xposed worked for me in Oreo 8.0, but has not worked since upgrading to 8.1. I get the same bootloop issue on OPW28.2.

AvenidaDelGato said:
Which Stock ROM version are you using? Xposed worked for me in Oreo 8.0, but has not worked since upgrading to 8.1. I get the same bootloop issue on OPW28.2.
Click to expand...
Click to collapse
Thank you, that's good to know because I'm also on 8.1, so it sounds plausible that it's not just me, but a larger compatibility issue between Xposed and 8.1. on this phone.

Just an update, I ended up flashing a factory 8.0 ROM via fastboot and, while it still fails SafetyNet (CTS Profile Mismatch) for some reason, I was able to get Xposed running and finally start using the phone as my primary device. So it is likely to be an 8.1 compatibility issue on this device that was giving me trouble before. Now hopefully I can find a version to flash that will pass SafetyNet, but until then, this will suffice. Thanks for everyone's help!

dcdruck1117 said:
Just an update, I ended up flashing a factory 8.0 ROM via fastboot and, while it still fails SafetyNet (CTS Profile Mismatch) for some reason, I was able to get Xposed running and finally start using the phone as my primary device. So it is likely to be an 8.1 compatibility issue on this device that was giving me trouble before. Now hopefully I can find a version to flash that will pass SafetyNet, but until then, this will suffice. Thanks for everyone's help!
Click to expand...
Click to collapse
I've been putting off unlocking bootloader due to my recent concerns with these ota patches being released.
If safetynet fails, what can you not use besides Pay? It's to my understanding safetynet is now being incorporated to several applications and failing, will result in a sometimes inoperable app altogether?

dcdruck1117 said:
I've tried both: installing via Magisk Manager as well as flashing zip in TWRP (xposed-v90.2-sdk27-beta3-topjohnwu.zip). Similar results in both cases.
Click to expand...
Click to collapse
Use EdXposed, works for me, and pass Safetynet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Blind app is detecting root with Magisk Hide

I've got an app I'd like to use that somehow keeps detecting root. It's called Blind (https://play.google.com/store/apps/details?id=com.teamblind.blind)
I've also got Pokemon Go installed, but that works just fine. Not problems with Magisk Hide.
I'm ready and willing to provide logs and such, just not sure where I should start.
Thanks!

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot

mew1033 said:
I've got an app I'd like to use that somehow keeps detecting root. It's called Blind (https://play.google.com/store/apps/details?id=com.teamblind.blind)
I've also got Pokemon Go installed, but that works just fine. Not problems with Magisk Hide.
I'm ready and willing to provide logs and such, just not sure where I should start.
Thanks!
Click to expand...
Click to collapse
Did you ever figure it out?

Just. Tried too. For test lol.
Didn't work for me.
I'm having issue with spay for gear 3.
If you can figure it out and maybe we can also both our issues

It suddenly started working for me today...

I was having this issue too. I eventually got so frustrated, I unrooted my device, relocked the bootloader, and did a factory reset. Still thinks I'm rooted, even though I'm completely factory. I think they get some unique device identifier and block your device server-side
If anyone figures it out, please let me know.
A bit of an annoying workaround: if you can make a comment with a different phone, and you get a notification telling you someone replied, you can open the app by tapping on the notification. However, it won't work if you open it by tapping on the icon

Any update?
Tried a whole bunch of things to hide Magisk. Blind just doesn't work.

Works!
Looks like Blind is detecting if your bootloader is unlocked. I installed this Magisk module called "SafetyPatch", which prevents apps from detecting if your bootloader is unlocked. That fixed it for me!

Darn, tried installing SafetyPatch, but still no luck
I suspect my phone has been blacklisted or something

I had checked logcat and it seems that blind was using com.liapp.lockincomp to detect root and display the alert. after hiding magisk manager and using magisk hide on blind it still didn't work even after clearing data/reinstalling the app. after a few days it magically started working again. guess they blacklist devices for x amount of time after they detect root.

I had Blind 2.5 and Magisk 17 working together. About two weeks ago I updated both and it stopped working. Anyone using Blind 2.6 with Magisk 18? I think my device got banned - downgrading Blind to 2.5 didn't help.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seeing the issue on Blind 2.6.4 with Magisk Hide Enabled. Any other suggestions on a workaround?

Waited one week, installed Blind 2.5 from a backup and it works fine with Magisk 18.

babelus said:
Waited one week, installed Blind 2.5 from a backup and it works fine with Magisk 18.
Click to expand...
Click to collapse
So you uninstalled it & re-installed it after a week?
When you say backup, do you mean an APK that you had backed or a backup taken from TiBackup?

1nv1n said:
So you uninstalled it & re-installed it after a week?
When you say backup, do you mean an APK that you had backed or a backup taken from TiBackup?
Click to expand...
Click to collapse
Correct, uninstall Blind, wait a week, reinstall from backup of APK (TitaniumBackup). I can share the APK, but you shouldn't trust me.

I uninstalled Blind. Uninstalled Xposed. Made sure Magisk was able to pass all SafetyNet checks. Re-installed Blind from the Play Store. Used Magisk to hide it & was able to launch it without issues.

1nv1n said:
I uninstalled Blind. Uninstalled Xposed. Made sure Magisk was able to pass all SafetyNet checks. Re-installed Blind from the Play Store. Used Magisk to hide it & was able to launch it without issues.
Click to expand...
Click to collapse
Thanks for sharing, this worked for me
(Rooted stock Moto Z2 Force with Oreo)

Looks like it's broken again? I tried following the same process; but even after being hidden through Manager, it's still able to detect either root or bootloader unlock.
Anyone got any ideas?

1nv1n said:
Looks like it's broken again? I tried following the same process; but even after being hidden through Manager, it's still able to detect either root or bootloader unlock.
Anyone got any ideas?
Click to expand...
Click to collapse
I can confirm my workaround using the old version of Blind stopped working. New version works for a day or two after installation, then it detects root and I have to uninstall and wait for the ban to expire.

How many days does the ban last for?