Database Develop

Xposed not installing?

So I rooted with the towelpieroot method on my 4.4.2 Verizon Non-Dev Moto X. And Xposed won't install. I keep getting either a Root not detected, Write error, or I/O error. Here is a screenshot:
{
"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 want to atleast be able to try it on my Moto X before the 4.4.4 update rolls around so I can decide if I want to delay it or not, if it lets me.
So any idea?
I used Root checker and I have root, and I tried this Mount System R/W app on the playstore because I don't know how to use ES explorer to do it. Still not working.

The only way I've been able to get exposed to work is using just pie root. There is a moto x tool kit which makes it easy but you have to use your computer. I can't get exposed to install with towel root or pietowel root. I'm on 4.4.2 with locked bootloader
Sent from my XT1058 using Tapatalk

superp32 said:
The only way I've been able to get exposed to work is using just pie root. There is a moto x tool kit which makes it easy but you have to use your computer. I can't get exposed to install with towel root or pietowel root. I'm on 4.4.2 with locked bootloader
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Alright, I heard some people had sucess but I guess not. So how would I go about un-rooting and rooting with this tool kit? (Where is it? Is it just the pie root thread?)

Just reboot to unroot any of the methods except pietowel if you clicked root on reboot then go to development section look for moto x tool kit I'd give you the link but I'm on my phone. Then use pie root its Jcases work but I think the tool kit just includes it.
Sent from my XT1058 using Tapatalk

superp32 said:
Just reboot to unroot any of the methods except pietowel if you clicked root on reboot then go to development section look for moto x tool kit I'd give you the link but I'm on my phone. Then use pie root its Jcases work but I think the tool kit just includes it.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Alright so I unchecked the towelpieroot from rooting on reboot, and used the Moto X Toolkit. I got Xposed to install, and thats it. Do I have to re-root each time I reboot to install a module? I did, and now I don't have root acess and the tool kit isn't working, it keeps checking for adb for quite a while now.

OK so when you plug in your phone it brings up a rsa code or something turn off USB debugging then turn it back on it should bring that up then reroot also don't reboot install the power menu module so you can soft reboot instead of going through the rerooting process every time
Sent from my XT1058 using Tapatalk

TechTinker said:
So I rooted with the towelpieroot method on my 4.4.2 Verizon Non-Dev Moto X. And Xposed won't install. I keep getting either a Root not detected, Write error, or I/O error. Here is a screenshot:
I want to atleast be able to try it on my Moto X before the 4.4.4 update rolls around so I can decide if I want to delay it or not, if it lets me.
So any idea?
I used Root checker and I have root, and I tried this Mount System R/W app on the playstore because I don't know how to use ES explorer to do it. Still not working.
Click to expand...
Click to collapse
For what it's worth, every time I reboot I need to try TowelPieRoot and Xposed 4-5 times before it will finally stick. I don't know why, but it is very difficult to get it to work.
I also got the same error as above in your screenshot. I can only have success in applying Xposed after a fresh, full reboot. If I do anything else with my phone first, I get the error.
Here is what I do:
1. Full reboot of phone
2. I wait 1-2 min for everything to completely start up and load (including any autorun apps or notification background processes -- I do not touch the phone or open any apps while I'm waiting)
3. Run TowelPieRoot
4. Use Root Checker or better yet, Busybox Checker to verify root and Busybox installed
5. Open Xposed, go to Framework, tap Install/Update
6. Back out of the reboot dialog and then tap Soft Reboot
From there, the phone will usually initiate a soft reboot. Sometimes, the phone will make it through and begin reloading any startup processes. I am careful not to touch the phone for 2 min while it does its thing. But most times, it fails and will do a hard reboot on its own. Back to square one. Using Root Checker verifies that I don't have root anymore.
So I do it again from step 1. As I mentioned, I go through the steps 4-5 times before finally, the soft reboot works, all startup items are loaded, and going into Xposed shows that it is running and up to date.
Obviously, this isn't very scientific. But, try it in succession a few times and see if it works.

same problem for me with towel pie root

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?

Journey between ROMs is PAINFUL!

This is a question - NOT a complaint.
I was able to unlock, reroot and get to CF newest 5.1 with no issues (was on Mofo Root version). I saw RR and CM12 Rom conversations pop up, so I gave RR a run. I downloaded ROM and Gapps, wiped all dalvik, cache, system, etc (not internal card), installed and it started up without issues. At first. Started to get services closing, then play store closing, etc. It snow balled. Was able to key my way into recovery.
I said heck with this, I must've screwed up. So I wiped caches again - and same thing happened restarting. Back to recovery, wipe all, reinstall CF's that I had nandroid of.
Restart - same thing!!! WFT.
Back to recover, wipe all, install clean CF version and start up - no issues. So, I'm back at square 1.
Question - I recall years ago, I used to get into trouble going back and forth between CM and AOSP ROMs on same phone. I forget what I did to cause the issues, or how I fixed them. Can some one tell me, is this the same thing happening?
Is there something one needs to do to go back and forth between RR and CF ROM? Does wiping system cause issues? Should I wipe system all the time?
Having BL unlock is amazing as it is really hard to kill this thing following even the most basic instructions - but seems I'm causing some issues.
Any help appreciated!

What gapps are you using?
Sent from my DROID Turbo using XDA Free mobile app

Also, after you did the factory reset in TWRP, then installed RR and Gapps, did you try to restore anything from previous CF installation to your new installation? One guy tried to do that. He tried to use TWRP to restore data and I guess apps from old Verizon-based ROM to his new ROM. Stuff from a totally different ROM!
So, just asking.
Because if you did a factory re-set in TWRP, then flashed Resurrection Remix and the recommended GAPPS, and then re-downloaded any apps you need from the Google Play store, that's what we call a clean install and everything should work fine...
{
"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"
}

ChazzMatt said:
Also, after you did the factory reset in TWRP, then installed RR and Gapps, did you try to restore anything from previous CF installation to your new installation? One guy tried to do that. He tried to use TWRP to restore data and I guess apps from old Verizon-based ROM to his new ROM. Stuff from a totally different ROM!
So, just asking.
Because if you did a factory re-set in TWRP, then flashed Resurrection Remix and the recommended GAPPS, and then re-downloaded any apps you need from the Google Play store, that's what we call a clean install and everything should work fine...
Click to expand...
Click to collapse
Did you hear that? That slapping sound? That was me smacking my forehead and nearly passing out.
D'oh!!!!!!!! Yes. I TIBU'd my apps/data. After following RR install steps (including the enclosed gapps from that RR OP), I reloaded everything from TIBU restore. Crap. Makes me wonder too if that did enough "damage" that my restore of CF did work right then either. Nuts.
So, thanks for the idea. As a closet flash addict, I'll try again. I mean......... I just have to, right?

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?

Question Root and partial debloat, cannot connect to Xiaomi Account

Hi everyone,
I've rooted my device a long time ago, rom updated and re-root many times. On first time I've partially debloat my phone.... (I've followed this guide)
Since first day I cannot use the Xiaomi account connection, but I've got a smartwatch recently and the mi account connexion is prerequire.
So i've decide to finally look what is going wrong with it.
When I attempt to connnect to Mi Account, it seem to access to sim data. After some time nothing happend and i can skip the sim check.
After skipping, I can choose to connect with my xiaomi user/mdp or with my google account. They all loop in checking security datas... and crash
when it crash the bug report a java.lang.NullPointerException in a Method called android.database.Cursor.moveToFirst(). with some references to com.xiaomi.account and com.xiaomi.finddevice
Perhaps its a bloat that i've unistalled, perhaps it's a firewall rule... I really dont know.
Can somebody provide me some help?

That's it, you have deleted necessary functions.
Reinstall the missing functions or reinstall the rom and if really necessary root the phone.
Tools for debloating without root. (one is no longer updated, but works very well)
https://forum.xda-developers.com/t/...mate-app-manager-debloat-tool-tweaks.4147837/
https://szaki.github.io/XiaomiADBFastbootTools/

I've check all apps. They said their is no deleted app. Only one disabled "de.telkom.tsc". But after multiple attempt I havent't manage to enable again.
Can I do anything more with theses apps?

AlexGhost67 said:
I've check all apps. They said their is no deleted app. Only one disabled "de.telkom.tsc". But after multiple attempt I havent't manage to enable again.
Can I do anything more with theses apps?
Click to expand...
Click to collapse
You deleted the apps by Cmd and not with a program.
Reinstalled the rom or tried to find the corresponding apk

Is it a way to find what app can be missing? I've done this delete by cmd a few year ago... my memory isn't as good!

AlexGhost67 said:
Is it a way to find what app can be missing? I've done this delete by cmd a few year ago... my memory isn't as good!
Click to expand...
Click to collapse
Certainly:com.xiaomi.account and com.xiaomi.finddevice
But it will not be easy to find the versions corresponding to your rom.
Reinstalling the rom you lose root but not your data.

I reinstalled all the missing apps from the bloat list that I think I tracked at the time. Unfortunately there is no change.
com.xiaomi.account and com.xiaomi.finddevice are installed and active
You said reinstalling the rom you lose root but not your data. You mean do a factory reset?

AlexGhost67 said:
I reinstalled all the missing apps from the bloat list that I think I tracked at the time. Unfortunately there is no change.
com.xiaomi.account and com.xiaomi.finddevice are installed and active
You said reinstalling the rom you lose root but not your data. You mean do a factory reset?
Click to expand...
Click to collapse
Xiaomi sim activate service?
Xiaomi services frameworks?

All good..

AlexGhost67 said:
All good..
Click to expand...
Click to collapse
That's to say?

No excuse me, all apps are installed.
The bug is still there.
I think I must take a look to a old fashioned factory reset...

AlexGhost67 said:
No excuse me, all apps are installed.
The bug is still there.
I think I must take a look to a old fashioned factory reset...
Click to expand...
Click to collapse
Check here that your device appears and that there are no duplicates.
Factory data you will lose your data, try to download the package from the updater, 3 points at the top right.

NOSS8 said:
Factory data you will lose your data, try to download the package from the updater, 3 points at the top right.
Click to expand...
Click to collapse
I've already use the updater to update my rom recently. So use these way doesn't clear my bug.
I've attempt to connect before root again last time, and it's doesn't work unrooted...
Their is no duplicates in my Xiomi account.

AlexGhost67 said:
I've already use the updater to update my rom recently. So use these way doesn't clear my bug.
I've attempt to connect before root again last time, and it's doesn't work unrooted...
Their is no duplicates in my Xiomi account.
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
with a fastboot rom and dont re lock the bootloader.

NOSS8 said:
Try https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
with a fastboot rom and dont re lock the bootloader.
Click to expand...
Click to collapse
The last way, the hard way!! All data erased...
I'll try on weekend. It's my all day phone so I can't lose it during a job day.
Perhaps an other solution came during the week. Thks for all you've done!

{
"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"
}