Flashed the 6.0.1 stock image coming from mra58x. Rooted with systemless root and franco kernel and busybox. Since the update, I haven't been able to use WiFi calling. I'm also noticing that I can't send or receive mms on WiFi. Had no issues prior to the uodate. Flashed the 30r radio and that didn't help. Anyone else have these issues?
goinflyn said:
Flashed the 6.0.1 stock image coming from mra58x. Rooted with systemless root and franco kernel and busybox. Since the update, I haven't been able to use WiFi calling. I'm also noticing that I can't send or receive mms on WiFi. Had no issues prior to the uodate. Flashed the 30r radio and that didn't help. Anyone else have these issues?
Click to expand...
Click to collapse
I haven't had problems with wifi calling on 6.0.1. Does it work at all? Like can you turn on airplane mode, then turn on wifi.
Dosent work at all. Been combing through all the threads and its either the kernel or the root. I'm going to reflash the system image and see if I can isolate what's breaking WiFi calling. I have a feeling it's the kernel, but we'll see.
goinflyn said:
Dosent work at all. Been combing through all the threads and its either the kernel or the root. I'm going to reflash the system image and see if I can isolate what's breaking WiFi calling. I have a feeling it's the kernel, but we'll see.
Click to expand...
Click to collapse
Yeah kernel would be my first guess. Theoretically root in itself should be fine.
cupfulloflol said:
Yeah kernel would be my first guess. Theoretically root in itself should be fine.
Click to expand...
Click to collapse
na, not roots fault. i have root, and a custom kernel, and wifi calling works.
I had the same problem, I thought it was because of the new 2.64 SuperSU, reverted back to 2.61, still broken. I remember it was working before, I read somewhere that busybox maybe the culprit, uninstalled busy box wifi calling pops right up.
edit. Just updated back to 2.64 SuperSu, wifi calling is all good now, busybox still uninstalled.
For me it was the kernel. Deleted busybox, no change. Flashed stock ROM, WiFi calling worked. Flashed twrp, still worked. Flashed 2.64 root, still worked. Must be the Franco kernel. I was on r38. Do I really need a custom kernel?
I stand corrected, it was busybox that broke WiFi calling. I flashed r39 and WiFi still worked. Flashed busybox and lost WiFi calling.
Try toybox instead, it's even part of AOSP now.
Sent from my Nexus 6 running cyosp using Tapatalk
Do you have a link or is it in the play store?
goinflyn said:
Do you have a link or is it in the play store?
Click to expand...
Click to collapse
I don't know, I didn't see it in the play store, but you might find it here on xda.
My rom is AOSP based, it already has it.
i can confirm that uninstalling busybox fixed the issue
goinflyn said:
I stand corrected, it was busybox that broke WiFi calling. I flashed r39 and WiFi still worked. Flashed busybox and lost WiFi calling.
Click to expand...
Click to collapse
Man, this was driving me nuts!! Seems it IS busy box, as it was working with EX kernel fine. Just to test I downloaded and installed busy box, at first I still had wifi calling. I figured must be something else (clean flash). I checked a min later and saw no service on lock screen instead of wifi calling. I uninstalled busy box and still no wifi calling. I rebooted. Nope. I'd rather not start clean again but will do if necessary. Any ideas? It just started working after you uninstalled busy box? Do you actually install it in the busy box app (stupid just throwing it out there)? Thanks!
ConTejas2 said:
Man, this was driving me nuts!! Seems it IS busy box, as it was working with EX kernel fine. Just to test I downloaded and installed busy box, at first I still had wifi calling. I figured must be something else (clean flash). I checked a min later and saw no service on lock screen instead of wifi calling. I uninstalled busy box and still no wifi calling. I rebooted. Nope. I'd rather not start clean again but will do if necessary. Any ideas? It just started working after you uninstalled busy box? Do you actually install it in the busy box app (stupid just throwing it out there)? Thanks!
Click to expand...
Click to collapse
guess what? you are wrong:
its not busybox. as I'm on 6.0.1, have busybox installed, on tmobile, and have WiFi calling working..
what it can be is which busybox are you using?
{
"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 posted the version of busybox I was using. I had to reflash the system, boot and cache files and reinstall systemless root and twrp. I stopped using a custom kernel and just run the stock kernel with root.
goinflyn said:
I posted the version of busybox I was using. I had to reflash the system, boot and cache files and reinstall systemless root and twrp. I stopped using a custom kernel and just run the stock kernel with root.
Click to expand...
Click to collapse
ahh stericsons version, good man.. its the same one I'm using(always). so it can't be it, as for WiFi calling is working here fine on tmobile and 6.0.1.
simms22 said:
guess what? you are wrong:
its not busybox. as I'm on 6.0.1, have busybox installed, on tmobile, and have WiFi calling working..
what it can be is which busybox are you using?
Click to expand...
Click to collapse
simms22 said:
ahh stericsons version, good man.. its the same one I'm using(always). so it can't be it, as for WiFi calling is working here fine on tmobile and 6.0.1.
Click to expand...
Click to collapse
I very well may be wrong, but WiFi calling worked fine until installing busy box. It doesn't work even after uninstalling. It was working fine even with a custom kernel (ex). I've started clean a few times now. Always seems to be busy box. I do delete /su/bin_bind for AP. I'll start clean without doing that and see
ConTejas2 said:
I very well may be wrong, but WiFi calling worked fine until installing busy box. It doesn't work even after uninstalling. It was working fine even with a custom kernel (ex). I've started clean a few times now. Always seems to be busy box. I do delete /su/bin_bind for AP. I'll start clean without doing that and see
Click to expand...
Click to collapse
Sorry, but Stericson's BB (the free version) does seem to have something to do with it. I had noticed it not working and put on back burner. I'm working remotely today and needed to fix it, ran across this thread. Uninstall from inside the app, remove the app, and then toggle airplane mode and it suddenly worked fine (after having not been working reliably for over a week). Does the BB path take first order?
Related
So I decided I should to a factory reset on my Moto X today to clean it up and make it run better. Anyway I downloaded Towel Pie Root, rooted the phone, and backed up my apps with TB. My phone hadn't been rooted up to this point. Anyway I did the app backup and pulled my /sdcard/ contents to my laptop with adb and did the factory reset. Afterwards I got everything updated, restored the apps I wanted with TB(after rerooting with TPR), and got the phone set back up like I wanted. I also decided I'd give Xposed a try being that rooting was fairly simple with TPR. I downloaded Xposed 2.6.1, installed the framework and did a soft reboot. After doing that I can't connect to WiFi anymore; I just get a "Failed to Connect to Network" toast notification when I try. A Hard Reboot fixes the issue until I reinstall Xposed then WiFi breaks again.
Any ideas on why this is happening or how to fix it? I know I read in the TPR thread that people were using Xposed with TPR like I'm trying to.
Sent from my MacBook Pro using Chrome
Phone: Moto X(XT1053) running Stock 4.4.3
Xposed causes WiFi to stop working... fix
NOW firstly uninstall your xposed installer ,And the download the latest version v7.1 from repo.xposed.info/module/de.robv.android.xposed.installer
& install it..
IT SHOULD WORK..
& SORRY FOR MY ENGLISH
prashantsingh480 said:
NOW firstly uninstall your xposed installer ,And the download the latest version v7.1 from repo.xposed.info/module/de.robv.android.xposed.installer
& install it..
IT SHOULD WORK..
& SORRY FOR MY ENGLISH
Click to expand...
Click to collapse
No luck....
{
"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"
}
Now it's not even seeing that there are networks in the area. [emoji20]
Sent from my Moto X (XT1053) using Tapatalk
Now it's not even seeing that there are networks in the area. [emoji20]
Sent from my Moto X (XT1053) using Tapatalk[/QUOTE]
first uninstall the xposed installer & then check if it catches the wifi network or not ..... :good::good:
Deleted
The WiFi starts working after a hard reboot which makes xposed not work because I lose root after a hard reboot. Whether or not the xposed installer is installed or not doesn't make a difference. My WiFi is fine now that I did a hard reboot.
Sent from my Moto X (XT1053) using Tapatalk
tnp9008 said:
The WiFi starts working after a hard reboot which makes xposed not work because I lose root after a hard reboot. Whether or not the xposed installer is installed or not doesn't make a difference. My WiFi is fine now that I did a hard reboot.
Sent from my Moto X (XT1053) using Tapatalk
Click to expand...
Click to collapse
NOW ,root your moto X by root master .
& check if it catches the networks or not if it catches.
the install xposed installer v7.0 not the latest (v7.1).
then check ...
SHOULD WORK ......
BEST OF LUCK....
Does your phone reset the system partition after reboot?
If so... Try flashing xposed... Switch install method to manual recovery flash... Run the installer... Then reboot to recovery and flash the zip...
MotoX has a nasty system reset thingy... You have to look for the workaround in your device thread...
Why its borking WiFi... I'm not sure
rignfool said:
Does your phone reset the system partition after reboot?
If so... Try flashing xposed... Switch install method to manual recovery flash... Run the installer... Then reboot to recovery and flash the zip...
MotoX has a nasty system reset thingy... You have to look for the workaround in your device thread...
Why its borking WiFi... I'm not sure
Click to expand...
Click to collapse
I know my system partition is read only. The only way to have read/write is to unlock my bootloader which I could do but I don't want to lose my warranty so that's not an option right now. When the warranty runs out I plan to get an unlock code and obtain full root with system read/write but that's a ways off. I don't have custom recovery installed so I can't flash manually in recovery; the root access I gain is temporary. I have to re-root with Towel Pie Root after every full reboot. From what I read in the TPR thread people have had success using xposed on the Moto X like I'm doing, but for some reason it borks my WiFi.
Update: After digging through the TPR thread it looks like this is a somewhat common issue with TPR + 4.4.3 + Xposed. The TPR dev is looking into the issue.
Is your WiFi Calling staying connected after updating to 10n? Mine was working fine on 10h, but on 10n it disconnects after 5-10 minutes with a REG99: Unable to connect error and won't reconnect until I reboot the phone.
I did all the troubleshooting steps with T-Force: factory reset, got a new SIM card, got an update sent to the SIM card twice, factory reset again, and no dice.
Is anyone else experiencing this on 10n? I'm on stock rooted 10n (odex).
EDIT: It's XPosed. As long as the XPosed Framework is installed (even with no modules), WiFi Calling is completely broken.
I was getting the same error on 10N. I called and was transferred to Tech Support. They updated my E-911 info and was back up in running in less than 5 minutes
siraltus said:
Is your WiFi Calling staying connected after updating to 10n? Mine was working fine on 10h, but on 10n it disconnects after 5-10 minutes with a REG99: Unable to connect error and won't reconnect until I reboot the phone.
I did all the troubleshooting steps with T-Force: factory reset, got a new SIM card, got an update sent to the SIM card twice, factory reset again, and no dice.
Is anyone else experiencing this on 10n?
Click to expand...
Click to collapse
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
jamesd1085 said:
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
Click to expand...
Click to collapse
I'm using xposed and it works great (wi-fi calling).
gerald410 said:
I'm using xposed and it works great (wi-fi calling).
Click to expand...
Click to collapse
Not the case for me and others are trickling in with the same issue
So I rooted my phone a little more than a week ago and then flashed MicroMod777's rooted stock 10n ROM a few days later. Up until this point, WiFi calling was working. I then flashed the Xposed framework v72, downloaded some modules, and installed them. I realized that WiFi calling was no longer available and would give me the classic REG99 error, unable to connect. Another user on MicroMod777's 10n stock ROM thread (http://forum.xda-developers.com/tmo...m-g4-h811-10n-stock-rooted-rom-t3188858/page9) had the same problem, though another user responded that Wifi calling was working fine with the 10 ROM and Xposed v72.
I uninstalled Xposed and I could immediately access WiFi calling, so it seems that Xposed is conflicting with the 10n stock ROM's WiFi calling. Same results with v73. Users who are getting WiFi calling to work on Xposed, did you get the official 10n update OTA or flash a rooted ROM? And what version of Xposed are you running?
Synchronicities said:
So I rooted my phone a little more than a week ago and then flashed MicroMod777's rooted stock 10n ROM a few days later. Up until this point, WiFi calling was working. I then flashed the Xposed framework v72, downloaded some modules, and installed them. I realized that WiFi calling was no longer available and would give me the classic REG99 error, unable to connect. Another user on MicroMod777's 10n stock ROM thread (http://forum.xda-developers.com/tmo...m-g4-h811-10n-stock-rooted-rom-t3188858/page9) had the same problem, though another user responded that Wifi calling was working fine with the 10 ROM and Xposed v72.
I uninstalled Xposed and I could immediately access WiFi calling, so it seems that Xposed is conflicting with the 10n stock ROM's WiFi calling. Same results with v73. Users who are getting WiFi calling to work on Xposed, did you get the official 10n update OTA or flash a rooted ROM? And what version of Xposed are you running?
Click to expand...
Click to collapse
Stocked rooted rom and v72 I believe (how to confirm?).
gerald410 said:
Stocked rooted rom and v72 I believe (how to confirm?).
Click to expand...
Click to collapse
Open the XPosed Installer app and look in the Framework section.
jamesd1085 said:
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
Click to expand...
Click to collapse
I was having the issue on a totally stock, factory-reset phone with nothing installed.
T-Force opened a ticket with network engineering, supposed to be resolved by tomorrow.
siraltus said:
Not XPosed's fault at all. I was having the issue on a totally stock, factory-reset phone with nothing installed.
Click to expand...
Click to collapse
Just asking as i have same issue but only with xposed...as are some others
jamesd1085 said:
Just asking as i have same issue but only with xposed...as are some others
Click to expand...
Click to collapse
Interesting.... I wonder why. I have Xposed installed on my Note 4 also and WiFi Calling works perfectly fine there. Might be a specific module causing it.
Come to think of it, when I factory-reset the phone, Xposed was still installed into the system partition, since it's not an app, but a modification to system files.
I will have to re-test after explicitly uninstalling Xposed. It would be a total bummer if Xposed is the problem. And if it is, I hope it's just a specific module that I can disable. I'd hate to lose YouTube AdAway and a few others.
siraltus said:
Interesting.... I wonder why. I have Xposed installed on my Note 4 also and WiFi Calling works perfectly fine there. Might be a specific module causing it.
Come to think of it, when I factory-reset the phone, Xposed was still installed into the system partition, since it's not an app, but a modification to system files.
I will have to re-test after explicitly uninstalling Xposed. It would be a total bummer if Xposed is the problem. And if it is, I hope it's just a specific module that I can disable. I'd hate to lose YouTube AdAway and a few others.
Click to expand...
Click to collapse
Mine is broken without even adding modules...fixes instantly after flashing xposed uninstaller
jamesd1085 said:
Mine is broken without even adding modules...fixes instantly after flashing xposed uninstaller
Click to expand...
Click to collapse
Well that just sucks. I just uninstalled Xposed and WiFi Calling is staying connected now. This is not good.
siraltus said:
Well that just sucks. I just uninstalled Xposed and WiFi Calling is staying connected now. This is not good.
Click to expand...
Click to collapse
Looks like we need to try and get some logs for rovo and hopefully he can easily fix it...
Scrap that! Download SELinux mode changer and change to permissive...instantly popped up and stayed connected! Great news
jamesd1085 said:
Looks like we need to try and get some logs for rovo and hopefully he can easily fix it...
Scrap that! Download SELinux mode changer and change to permissive...instantly popped up and stayed connected! Great news
Click to expand...
Click to collapse
O RLY... is that an Xposed module?
siraltus said:
O RLY... is that an Xposed module?
Click to expand...
Click to collapse
Try ticking disable resource hooks in exposed installer app...and You can google SELinux mode changer its an app it coonects after boot...takes longer than it used to but its working on my end
siraltus said:
Open the XPosed Installer app and look in the Framework section.
Click to expand...
Click to collapse
I'm running v71 thx.
jamesd1085 said:
Try ticking disable resource hooks in exposed installer app...and You can google SELinux mode changer its an app it coonects after boot...takes longer than it used to but its working on my end
Click to expand...
Click to collapse
Nope, neither works. WiFi Calling is still busted while Xposed is installed.
siraltus said:
Nope, neither works. WiFi Calling is still busted while Xposed is installed.
Click to expand...
Click to collapse
Try unticking disable hooks...it's working fine without that...try a couple reboots...mine has settled in and works fine...also did you opeen the app and grant root and press permissive?
jamesd1085 said:
Try unticking disable hooks...it's working fine without that...try a couple reboots...mine has settled in and works fine...also did you opeen the app and grant root and press permissive?
Click to expand...
Click to collapse
Of course I granted root and pressed Permissive, I know what SELinux is. I also unticked that checkbox and rebooted like 5 times. It either never connects or connects and disconnects after 2-3 minutes.
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?
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"
}
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?