Database Users

4.4.2 and towelroot

has anyone tried this yet and does it work

Yes it does if you're on nc1 firmware
Sent from my Nexus 5 using XDA Free mobile app

I have tried this and everything says that the phone is rooted, however, when I open apps they are not asking for permission. Is there something else that I need to do? Apps that work only on rooted phones are working fine so I am kind of stumped. Any help would be appreciated.
Thanks.

bigtymehokie said:
I have tried this and everything says that the phone is rooted, however, when I open apps they are not asking for permission. Is there something else that I need to do? Apps that work only on rooted phones are working fine so I am kind of stumped. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
That's the way it works and part of the reason the exploit is scary, apps don't ask for permission.
Sent from my Nexus 5 using XDA Free mobile app

I have SuperSu installed and I do get prompts for granting or denying apps permission, but yeah if you don't have a Superuser access management tool, apps are granted root permissions immediately. If you don't want that custom boot logo and that's why you uninstalled SuperSu (if you even had it), you can use Wanam exposed and Xposed framework to fake system status and set it to official.

bigtymehokie said:
I have tried this and everything says that the phone is rooted, however, when I open apps they are not asking for permission. Is there something else that I need to do? Apps that work only on rooted phones are working fine so I am kind of stumped. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
Install SuperSu.

~wolverine~ said:
Install SuperSu.
Click to expand...
Click to collapse
I have SuperSU installed and that is what is confusing me. Sometimes it asks me to grant permission for apps I open and then other apps will open without asking any permissions.

bigtymehokie said:
I have SuperSU installed and that is what is confusing me. Sometimes it asks me to grant permission for apps I open and then other apps will open without asking any permissions.
Click to expand...
Click to collapse
Do the apps that open without notification need root permission? If they don't they won't ask for it.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Do the apps that open without notification need root permission? If they don't they won't ask for it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Here is what i am trying to do...I used to be able to get music from Google Play to Doubletwist with my rooted phone. I had to unroot it and then root it again. Doubletwist used to ask for permission, however now does not. Nor will the music move over. Long story short, that is what I am working on. Unsuccessfully, I might add. Last time I rooted the phone, I used the SD Card method and this time I used towelroot. Not sure if that would make a difference or not.

Android pay?

Anyone have this working? I'm rooted ,vzn, stock.
Sent from my XT1575 using Tapatalk 2

Search these forums. A thread on this topic already exists.
Sent from my XT1060 using Tapatalk

I can't seem to find anything useful... Mind enlightening me? Do I have to use a root cloak or something?
Sent from my XT1575 using Tapatalk 2

I have the app but it crashes every tie I try to add a card

Jay794 said:
I have the app but it crashes every tie I try to add a card
Click to expand...
Click to collapse
Ive been trying for weeks...nothing seems to work...all threads come up with nothing...someone should be able to figure this out

My girlfriend used an app on her rooted s6 to hide root during the initial setup. it allowed her to go through the whole setup. then once it was loaded and working, she unhid root and deleted the app
Mileage may vary, and afterwards, worst case scenario, you may need to reflash supersu in twrp. Not likely though
https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot

You can add cards 'rooted' (turn off SU, add card, turn SU back on) but you can't use it to tap and pay

Bootup said:
You can add cards 'rooted' (turn off SU, add card, turn SU back on) but you can't use it to tap and pay
Click to expand...
Click to collapse
There was/is a big thread on this. Once your phone is rooted, you can't use the phone to tap and pay with Android Pay. Even if you unroot. Confirmed by a Google employee who worked on Android Pay.
See discussion here and here.

I have had it working by using the su program to remove root . then reboot phone. Tap and pay then works. Not sure if everyone had the same results. But this worked for me. When I needed root back i just used su and put it back.
Sent from my XT1575 using Tapatalk

In superSU I just hid root and then I was able to add the cards that were already in my Google wallet account. Haven't tried tap and pay but I can do that tomorrow to confirm. I was afraid that the unlocked bootloader was gonna be a problem beyond the root issue but so far it isn't.
Sent from my XT1575 using Tapatalk

Hide my root will hide the SU binary and allow Android Pay to work but it not only hides the SU it disables ROOT until you unhide it...so any apps that need root will not work while this is hidden. If you hide the SU binary...you have to reboot before android pay will work....tap and pay...not fun...frustrating

Android Pay - Root, Unroot?

I am interested in using Android Pay but understand the phone cannot be rooted.
I am curious I am would be able to Root for whatever purposes, and the unroot for day to day use to retain the ability to use Android Pay. I am willing to stay on the stock rom and install if needed.
Thanks

MoreGone said:
I am interested in using Android Pay but understand the phone cannot be rooted.
I am curious I am would be able to Root for whatever purposes, and the unroot for day to day use to retain the ability to use Android Pay. I am willing to stay on the stock rom and install if needed.
Thanks
Click to expand...
Click to collapse
I've seen threads that say to disable supersu, add cards, and reenable supersu and it should work. However, I tried this on the 6 and it never worked. As of now there doesn't seem to be surefire way to get Pay to work while rooted. If xposed is made for 6.0 a root cloak should work, but I can't be sure. Others may be able to provide addition info on this.

theycallmerayj said:
I've seen threads that say to disable supersu, add cards, and reenable supersu and it should work. However, I tried this on the 6 and it never worked. As of now there doesn't seem to be surefire way to get Pay to work while rooted. If xposed is made for 6.0 a root cloak should work, but I can't be sure. Others may be able to provide addition info on this.
Click to expand...
Click to collapse
What if you root your phone, apply an adblock, change your dpi, etc....and then unroot, leaving your changes intact. Then will android pay work?

ArkAngel06 said:
What if you root your phone, apply an adblock, change your dpi, etc....and then unroot, leaving your changes intact. Then will android pay work?
Click to expand...
Click to collapse
Some reports say the a DPI change causes AP to fail.
As far as the other, that should work fine.

Can anyone confirm this..? No Adblock is killing me.

I'm curious about this too. I've read that with nexus devices your have to lock the boatloader again as well as unroot. But then I've also seen people say these root then unroot tricks only work for adding cards, not for actually paying with them. I really like the idea of Android pay and hope nfc payments spread more, but everyday I ask myself "how many stores have nfc payment today vs how many things could I do with root today..." Not sure how long I can hold out.

It would be nice if we had a definitive answer or steps on how to add Android Pay but keep root. I'm using a systemless root now but have modified mixer_paths to increase headphone volume. I'm thinking about flashing stock boot then trying to add a card then going back to the modified boot.

Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.

new root method
http://www.androidpolice.com/2015/1...d-root-without-touching-the-system-partition/
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
New root method that does not modify the /system

exSD said:
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
Click to expand...
Click to collapse
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?

Good article on just what SafetyNet (Googles tamper checking for Android pay) does behind the scenes:
https://koz.io/inside-safetynet/
About 1/3 the way down the page it details the checks that are run to determine if the device has been tampered
Pretty interesting stuff, with a fairly important point: it does not reside on the actual device, its actually pulled down and run real-time when you fire up Android Pay. The interesting part about it is that could allow Google to disable some of the checks, to allow for things like Root, DPI changes, etc to actually NOT list the device as tampered. Will they? Who knows.

I have root and Android pay working fine. I've mad purchases multiple times this way
Sent from my Nexus 6P using Tapatalk

trebills said:
I have root and Android pay working fine. I've mad purchases multiple times this way
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You have systemless root.
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
That is what I'm saying.
You edit DPI by modifying your build.prop file. That file resides in /system.
If you make any change to /system, Android Pay will NOT work. Period. You can root cloak/add card/unroot after editing DPI/etc but when it comes time to actually pay, the SafetyNet will fail because you've modified your /system.

kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
Confirmed.
Here's the testing ive done:
Unlocked bootloader...AP works entirely.
rooted...AP will not allow you add a card, or process a transaction. If you have a card added prior to root, AP will not allow a transaction.
Disable root in SuperSu...AP will work entirely after you disable root and reboot your phone with root disabled. If you enable root again, AP will continue to work until you reboot.
With a modded DPI/no root...AP will not process a transaction.
Modified hosts file via Adfree/Adaway-root disabled...adblocking with a modified hosts file has no effect on AP
Click to expand...
Click to collapse
Those tests are all completed transactions at a terminal.

exSD said:
Guys - you cannot root with the /system way (the traditional way).
Modifying anything in /system will cause Android Pay to fail. That explains editing hosts, DPI, build.prop, etc. /system has to be clean otherwise when you go to actually pay it will fail but allow you to add your payment methods.
Click to expand...
Click to collapse
This is not universally true. I tested/verified a working method for using AndroidPay on a Sprint LG G3 that had a modified /system partition. Obviously that's a completely different phone, but it's one of the first things I'll be testing once my Angler comes in on Monday. Same method works for enabling adding cards the same as making a purchase. Here's what worked for me.
I got it figured out as well and so here's my method. I honestly think, though, that its every man for himself out there on this and that what works for one is unlikely to work for another.
Mine does not use XPosed, I don't have it installed. Requires use of SuperSU as your superuser manager and be currently rooted. I am running BarePapA-TE_V3 and NavelA-V1.6.
Download RootCloak Plus (Cydia) and Cydia Substrate from the Play Store.
Open Substrate. It tells me "Note: something about your device made it impossible for Substrate to perform its internal safety check; can you please contact saurik via e-mail?". Doesn't seem to effect anything.
Open RootCloak Plus (Cydia). Here you are going to be adding apps to a list of ones you don't want knowing you have root. There are a bunch of defaults already which you can leave. Add AndroidPay (com.google.android.apps.walletnfcrel). Now beyond that, I went ahead and added a number of other Google Apps and be certain any of them are required, but its what I did. I added the new Wallet app, Google Play Services, Play Store, Google Partner Setup, Google Account Manager, and Google Services Framework. Basically, my reasoning was that given the commitment to blocking rooted devices from using AndroidPay, it'd be useful to cloak any of the other financial apps and core GAPPS as well . . . because who knows how they are checking for root?
Reboot device.
Open SuperSU and uninstall superuser.
Reboot device. AndroidPay now works, buy yourself an Oreo McFlurry with your phone you clever hacker.
Obviously, your rooted apps won't work. So, if you want them back you will have to open SuperSU and reinstall superuser. That is going to break AndroidPay. Each time you want to use it again, you have to repeat the last two steps. So, there's the compromise . . . you can either leave your phone unrooted or have to reboot every time you want to use it.
Click to expand...
Click to collapse

cabbieBot said:
This is not universally true. I tested/verified a working method for using AndroidPay on a Sprint LG G3 that had a modified /system partition. Obviously that's a completely different phone, but it's one of the first things I'll be testing once my Angler comes in on Monday. Same method works for enabling adding cards the same as making a purchase. Here's what worked for me.
Click to expand...
Click to collapse
My phone is rooted in the normal way by flashing SuperSu.
If you change DPI on the phone it no longer passes a check of hardware configuration, so the device fails.
Other files have no effect. Hosts file does not describe HW so it doesn't matter.
Build.conf can be modified but not in areas that don't match the hardware.
I've had xposed installed after adding cards and added root cloak and had no isses.

I am rooted with system less root and android pay works fine. N6p angler.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
kolyan said:
Are you saying even if you edit DPI, Android Pay will not work ? Can anyone confirm this ?
Click to expand...
Click to collapse
That's correct do not edit stock dpi or pay will not work /at least as far as adding cards anyway (tested).

Thanks. I guess no AP for me. I root only to edit built.prop

puritan007 said:
I am rooted with system less root and android pay works fine. N6p angler.
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
That's correct do not edit stock dpi or pay will not work /at least as far as adding cards anyway (tested).
Click to expand...
Click to collapse
Rooted with system less root and Android Pay works....are you referring to it works without disabling root and rebooting? Or it just works regardless?
Seems there are some posts saying it works as long as you reboot with root disabled, and others saying "it works" but need clarification of any process that needed to be done before using it.

chrisexv6 said:
Rooted with system less root and Android Pay works....are you referring to it works without disabling root and rebooting? Or it just works regardless?
Seems there are some posts saying it works as long as you reboot with root disabled, and others saying "it works" but need clarification of any process that needed to be done before using it.
Click to expand...
Click to collapse
With any root before 5.46 you had to Un root to add cards. With 5.46 system less I did nothing it just works how it should with no messing about

Android Pay Working with Root

Here's how I have Android Pay working on my rooted 5x:
-Starting from stock 6.01 (Some other ROMs are reported working. Most importantly it needs to be a ROM where Android Pay was working prior to systemless root)
-Flashed systemless SuperSU 2.67 from TWRP (See UPDATE 3 below to make sure you have a systemless install)
-run "adb shell"
-from adb shell run "su"
-from adb shell run "chmod 751 /su/bin"
Have fun!
With this change the checks in SafetyNet Helper are passing and I can add cards and make purchases with Android Pay. The change is surviving reboots and doesn't require messing with any settings in the SuperSU app to enable/disable root.
UPDATE 1: As others have pointed out this permissions change can also be done with a file manager like Root Explorer that lets you change permissions. Probably easier for most than ADB commands.
UPDATE 2: Some people haven't been able to get Android Pay working with just this permission change. Check if you have /su/xbin_bind - deleting this may get it working. Thanks to @bobby janow and @CSX321 for pointing this out.
UPDATE 3: To clarify on the systemless SuperSU installation (this seems to be a trouble point for some) - there are settings that need to be configured for the SuperSU install to make it systemless and to not create the system/xbin binding. The installer reads these options from a file on /data/. Since you don't have root yet you need write these settings over ADB in TWRP. If you don't see the /su/ directory, you probably don't have a systemless install. In that case you can go back to stock (restore system, boot, and vendor partitions). Then, when you reinstall SuperSU, these are the commands you need to send from your TWRP ADB shell:
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Once you've got SuperSU installed, change the permissions of /su/bin/ (either chmod or using a file explorer)

You can check Android pay by simply trying to add a card and you'll know right away.

buru898 said:
You can check Android pay by simply trying to add a card and you'll know right away.
Click to expand...
Click to collapse
Yeah just removed my card and added it again. Went through all the contacting bank stuff and it worked. I think this is the real deal.

Try and make a purchase and report back! Thanks though!

Ya sometimes you can add a card but fail a purchase. Adding the card isn't a sure thing

jgummeson said:
Yeah just removed my card and added it again. Went through all the contacting bank stuff and it worked. I think this is the real deal.
Click to expand...
Click to collapse
Hmm now I want test this out. Need to flash ROM again.
If you're able to try a purchase, please let us know.

buru898 said:
Hmm now I want test this out. Need to flash ROM again.
If you're able to try a purchase, please let us know.
Click to expand...
Click to collapse
That's the only trouble with Android Pay - no one takes it. I'll see if I can stop by Trader Joe's tonight and pick something up. They're the only place around here I know of that takes it.

jgummeson said:
That's the only trouble with Android Pay - no one takes it. I'll see if I can stop by Trader Joe's tonight and pick something up. They're the only place around here I know of that takes it.
Click to expand...
Click to collapse
Don't forget anywhere you see the NFC lines symbol should work. I've even seen some that didn't have the symbol but still had an NFC scanner.
Sent from my Nexus 7 using Tapatalk

Yep Android Pay worked for a purchase. Just chmod your /su/bin/ directory to 751. Works for me on stock with systemless root and I imagine it may work on other ROMs that used to work until the recent change in the SafetyNet checks.

Running Chroma with SU 2.66. After running those commands AP will let me at least add a card, which I couldn't do before those commands (get can't verify android error). Will try testing in store tomorrow hopefully.

This is great news!
Tell the reddit people and get famous!

Does anyone know for certain if passing through SafetyNet Helper means it'll always work with pay?

smac7 said:
Does anyone know for certain if passing through SafetyNet Helper means it'll always work with pay?
Click to expand...
Click to collapse
Always? No. Google is actively trying to keep Android Pay safe in the eyes of banks and credit card companies, whether that is by blocking system/system-less root, or making adjustments server side to prevent workarounds that could potentially exploit the Android Pay experience.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Always? No. Google is actively trying to keep Android Pay safe in the eyes of banks and credit card companies, whether that is by blocking system/system-less root, or making adjustments server side to prevent workarounds that could potentially exploit the Android Pay experience.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well, i know google is trying to lock us out, but i thought safetynet was what Android pay uses to verify the the phone is indeed "safe". If the previous statement is correct, it would stand to reason that if it passes through safetynet helper then it'll also pass through android pay.

smac7 said:
Well, i know google is trying to lock us out, but i thought safetynet was what Android pay uses to verify the the phone is indeed "safe". If the previous statement is correct, it would stand to reason that if it passes through safetynet helper then it'll also pass through android pay.
Click to expand...
Click to collapse
That API is probably the best indicator of success right now but I could also see that changing if Google decides it needs to be more thorough in its approach
Sent from my Nexus 5X using Tapatalk

buru898 said:
This is great news!
Tell the reddit people and get famous!
Click to expand...
Click to collapse
Yeah I posted it on the Reddit and it sank to the bottom and everyone ignored it. No fame for me. I'll have to settle for Android Pay.

jgummeson said:
Yeah I posted it on the Reddit and it sank to the bottom and everyone ignored it. No fame for me. I'll have to settle for Android Pay.
Click to expand...
Click to collapse
Well you could always try having it posted to the xda portal and replying to this thread.
https://www.reddit.com/r/Android/comments/43bl05/newest_safetynet_check_detects_systemless_root/

buru898 said:
Well you could always try having it posted to the xda portal and replying to this thread.
https://www.reddit.com/r/Android/comments/43bl05/newest_safetynet_check_detects_systemless_root/
Click to expand...
Click to collapse
Yeah that's where I posted it - it's a comment way down on the bottom. Maybe I just don't know how to Reddit... Well started a new thread on there. Hopefully someone is paying attention this time.

jgummeson said:
Yeah that's where I posted it - it's a comment way down on the bottom. Maybe I just don't know how to Reddit... Well started a new thread on there. Hopefully someone is paying attention this time.
Click to expand...
Click to collapse
You just have to wait for somebody else to repost it:
https://www.reddit.com/r/Android/comments/44be69/android_pay_working_with_root/

jgummeson said:
Let me know if anyone else can confirm this works.
Click to expand...
Click to collapse
Yep! I just got a Mt. Dew from the machine at work. I did have to delete the card, reboot, and add the card back again. Pay seems to remember if it's ever failed with a card, and refuse to work with that card until you delete and re-add it.

Nexus 7 2012 on 5.1.1 -- any way to root it?

Hi all, kinda new to this whole game.
Couldn't find anything about rooting 5.1.1, only 4.2.2.
If there's no way to root 5.1.1, would you recommend reverting to 4.2.2 and then rooting it? Are there any improvements from using that version over 5.1.1?

Rooting 5.1.1 is the same way as on 4.2.2, unlock bootloader, flash custom recovery and flash super su.
I would recommend you to revert to 4.2.2 if you want a better performance, but if you want to stay on 5.1.1 make sure to use parrotmod to increase performance

Nexus Root Toolkit make it very easy.

thanks for the tips. i was able to root it, but now i'm trying to install the Xposed framework and it's telling me
cp:write error: No space left on device
meanwhile there's about 5 gigs of space since i flashed it down to 5.0 from 5.1.1
interestingly enough, after i root it and try to install busybox, it tells me free space is unavailable for /system/xbin as well as all the other options i try to change it to (/su/xbin, etc).
anyone know if something went wrong at some point?

PlayerThirteen said:
thanks for the tips. i was able to root it, but now i'm trying to install the Xposed framework and it's telling me
cp:write error: No space left on device
meanwhile there's about 5 gigs of space since i flashed it down to 5.0 from 5.1.1
interestingly enough, after i root it and try to install busybox, it tells me free space is unavailable for /system/xbin as well as all the other options i try to change it to (/su/xbin, etc).
anyone know if something went wrong at some point?
Click to expand...
Click to collapse
Your /system partition is full, try to remove something you don't need

iwjosi said:
Your /system partition is full, try to remove something you don't need
Click to expand...
Click to collapse
Thanks for the advice. How do I know what i can remove? If i flashed the tablet multiple times (tried diff versions of android), would that have bloated the /system partition?
Is there something specific i should be careful to leave in?

PlayerThirteen said:
Thanks for the advice. How do I know what i can remove? If i flashed the tablet multiple times (tried diff versions of android), would that have bloated the /system partition?
Is there something specific i should be careful to leave in?
Click to expand...
Click to collapse
you can remove google apps like youtube, hangout, g+ etc

anyone know if the play store can detect that a device is rooted, and prevent pokemon go from showing up in the store?
or is it just not detecting on my tablet possibly from the model of tablet i have?
i checked the official requirements page and there's nothing 'targeting' specific devices, the device just needs to haev Android 4.4+, but i'm not seeing it in my play store for whatever reason.
(my device is a nexus 7, Android 5.0)
i do recall that, before rooting my device, i'm pretty sure i was able to see and DL pokemon go on this tablet when it was running 5.11 before the root was performed

nvm, i found a site hosting the apk for the app. now just trying to make all the pieces work together on the nexus 7

you need to install Magisk to play pogo on a rooted tablet. magisk will disable the root so pogo will load.
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Flash a custom rom and install the nano gapps from http://opengapps.org/ if you want to install more apps.
But I wouldn't recommend it since it lags a lot without parrotmod speeding things up. Use the N7 2013 instead.

Magisk will not install on a 5..1.1 ROM because it needs systemless root and this is availabe only on 6.0 or greater ...

Thanks for the added tips. It's too bad this Magisk program only works on 6.0+.
I've tried everything detailed in this guide, including hiding the root with modules in Xposed, but i can't get the logins i created for PoGo to authenticate. I think i'm going to have to throw in the towel on this one.

AndDiSa said:
Magisk will not install on a 5..1.1 ROM because it needs systemless root and this is availabe only on 6.0 or greater ...
Click to expand...
Click to collapse
you might want to rethink that. It works fine on my 5.1.1, as stated in the magisk post "Magisk supports all the way down to Android 5.0 (SDK 21+) (thanks to the new method and busybox environment)"
---------- Post added at 03:21 AM ---------- Previous post was at 03:01 AM ----------
PlayerThirteen said:
Thanks for the added tips. It's too bad this Magisk program only works on 6.0+.
I've tried everything detailed in this guide, including hiding the root with modules in Xposed, but i can't get the logins i created for PoGo to authenticate. I think i'm going to have to throw in the towel on this one.
Click to expand...
Click to collapse
Don't use xposed, either don't install or disable when you don't need it. Someone mentioned that pogo won't work if xposed was installed, but i didn't think twice about it since mine worked with xposed installed, until today. So today I disabled xposed, then restarted, and it works again.

oh, thanks man. i'll def try it out -- see if i cant get it to work with Magisk. I appreciate you pointing that out

g96818 said:
you might want to rethink that. It works fine on my 5.1.1, as stated in the magisk post "Magisk supports all the way down to Android 5.0 (SDK 21+) (thanks to the new method and busybox environment)"
---------- Post added at 03:21 AM ---------- Previous post was at 03:01 AM ----------
Don't use xposed, either don't install or disable when you don't need it. Someone mentioned that pogo won't work if xposed was installed, but i didn't think twice about it since mine worked with xposed installed, until today. So today I disabled xposed, then restarted, and it works again.
Click to expand...
Click to collapse
Pardon my newb, but this workaround method is what i'm trying to achieve through all this.
In short, rooting, then using Xposed modules to hide the fact that 'mock locations' is enabled and faking my GPS location with it. (we live in a tiny town and want the device location moved to a big city).
Without Xposed installed, is there any alternate way that I can hide from PoGo that mock locations is enabled? Per the method linked, that was the one way to make it work, at time of writing.
Or even better, since the linked method actually didn't work on my device (pogo account 'wouldnt authenticate' -- not sure why but assuming its caused by xposed or some kind of root detection), would you know of a different way to fake my GPS location and hide it from PoGo on a Nexus 7?

Just to clarify, I followed your advice and installed Magisk already.
So I have a Magisk-ready device, just not sure where to take things from here, since I realized my instructions uses Xposed specifically to circumvent PoGo

Help
I'm in the same position.
How to remove thee apps? nexus tab 7 2012 is rooted running 5.1.1
Whic ROM should i use?

PlayerThirteen said:
Pardon my newb, but this workaround method is what i'm trying to achieve through all this.
In short, rooting, then using Xposed modules to hide the fact that 'mock locations' is enabled and faking my GPS location with it. (we live in a tiny town and want the device location moved to a big city).
Without Xposed installed, is there any alternate way that I can hide from PoGo that mock locations is enabled? Per the method linked, that was the one way to make it work, at time of writing.
Or even better, since the linked method actually didn't work on my device (pogo account 'wouldnt authenticate' -- not sure why but assuming its caused by xposed or some kind of root detection), would you know of a different way to fake my GPS location and hide it from PoGo on a Nexus 7?
Click to expand...
Click to collapse
There is another way, but it will disable your ability to use gps . use lucky patcher to install your spoofing app as a system app, then you don't need to enable mock locations and don't need xposed since the xposed modules don't work anyways. after that, install an app called disableservice and disable the 3 locationsharing services in google play service. What this does is prevent your real gps to overwrite your mock gps data.
try at your own risk of being banned

g96818 said:
There is another way, but it will disable your ability to use gps . use lucky patcher to install your spoofing app as a system app, then you don't need to enable mock locations and don't need xposed since the xposed modules don't work anyways. after that, install an app called disableservice and disable the 3 locationsharing services in google play service. What this does is prevent your real gps to overwrite your mock gps data.
try at your own risk of being banned
Click to expand...
Click to collapse
Thanks mate, i'll give it a shot!