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!
Related
I'm just wondering if anybody has managed to get the Sky Go app working with a rooted Nexus 7?
I've read somewhere that a rooted Android device can work with Sky Go if it is running a stock kernel and used in conjunction with Temp Root Remover.
If anybody has, please share your set up. :good:
Many Thanks,
Andy
I don't have an active Sky account anymore, but on Modaco JR13 with Stock kernel and unsecure boot.
I managed to load the app and sign into my old account without any problems.
Obviously I didn't get as far as watching TV as my account is closed.
Hope this helps.
+1 would like top know if it is possible
Sent from my Nexus 7 using XDA Premium HD app
This thread ( http://forum.xda-developers.com/showthread.php?t=2042095 ) describes a possible workaround (removal of supersu) but grants all subsequently installed apps root access after this, hence not ideal.
Fingers crossed a more secure method or patched apk arises in the future!
aaronje said:
This thread ( http://forum.xda-developers.com/showthread.php?t=2042095 ) describes a possible workaround (removal of supersu) but grants all subsequently installed apps root access after this, hence not ideal.
Fingers crossed a more secure method or patched apk arises in the future!
Click to expand...
Click to collapse
OK so I have a nexus 7 (2012) on standard Android 4.4.4.
Rooted with CWM and superSU 2.01
I just used the root hider app from the play store and selected ..
Hide Su binary and then
Uninstall super user (selected chain fire SuperSU option)
I then had to go into my root of my nexus 7 and remove the sky go files stored there.
After I deleted them I then restarted the tablet.
I can still reinstalled superSU as I'm still rooted but its a bit of a Hassel ATM as every time I want to watch SkyGO I have to follow the same routine, hideSu > uninstall superSU > delete SkyGO files from root dir > restart tablet.
I think there should be an Xposed module to hide root to certain apps, not 100% sure though..
A simple google search would answer your question: http://lmgtfy.com/?q=hide+root+access+android+xposed+module
But any ways here is the right module: http://repo.xposed.info/module/com.devadvance.rootcloak
It's called rootcloak. Remember: you need the Xposed Framework!
flopower1996 said:
A simple google search would answer your question: http://lmgtfy.com/?q=hide+root+access+android+xposed+module
But any ways here is the right module: http://repo.xposed.info/module/com.devadvance.rootcloak
It's called rootcloak. Remember: you need the Xposed Framework!
Click to expand...
Click to collapse
Still not working with the above, shame I just don't want to lose root.
jb.traveller said:
Still not working with the above, shame I just don't want to lose root.
Click to expand...
Click to collapse
hide su from google play works
1eyedmonster said:
hide su from google play works
Click to expand...
Click to collapse
Hi mate, could you give me a run down to what you did as I still can't get it to work.
Thanks.
1eyedmonster said:
hide su from google play works
Click to expand...
Click to collapse
I couldn't even find the app?
I rooted using the CF Auto method or whatever it was last week to try playing Hearthstone on my Note 4, however now my phone gets significant lag issues (screen locks up for 3-4 seconds every 5 minutes or so) and even stuttering while playing music over Spotify. Any ideas?
I uninstalled Xposed and the App Settings module to see if that would fix it, but it hasn't.
Brilliancy said:
I rooted using the CF Auto method or whatever it was last week to try playing Hearthstone on my Note 4, however now my phone gets significant lag issues (screen locks up for 3-4 seconds every 5 minutes or so) and even stuttering while playing music over Spotify. Any ideas?
I uninstalled Xposed and the App Settings module to see if that would fix it, but it hasn't.
Click to expand...
Click to collapse
hi,
i had similar and other experiences with Xposed and lag issue. (in past month) I have found that Xposed can break certain apps (when installing etc.. Shealth.. Play store, Samsung store, Private mode, and cause lag.
You must take into account that Xposed was last updated even before Note 4 was released.(?) So to me its not fully optimised? for Note 4?
However, I also found that Xposed broke certain apps.. even after i uninstalled it! eg.. My Play store was working fine with Xposed (Patched./fixes applied) and after i uninstalled Xposed i suddenly couldn't install apps from Play store! I was so fed trying to "fix" Play store etc... i just flashed my latest Official Rom over it..(All problems fixed!) So it could be Xposed that was original cause of your lag?.. even if you have uninstalled it? I have also found after uninstalling Xposed, some other module's functions are still present and i can still use it!
Just a pointer, maybe it helps?
good luck
Search the forum. It is S-Health, that causes lags, because it uses Secure Storage, which is not working with root. But there is a good news! There is already fix for it in custom kernels and XPosed Framework (search for SHealth in modules). You can use either.
Zer0r said:
Search the forum. It is S-Health, that causes lags, because it uses Secure Storage, which is not working with root. But there is a good news! There is already fix for it in custom kernels and XPosed Framework (search for SHealth in modules). You can use either.
Click to expand...
Click to collapse
I tried searching a bit, but wasn't finding any results for what little I knew. Sorry about that. Thanks a bunch for the help. Will simply disabling S Health solve the issues since I don't use it anyways?
Edit: Just realized you mentioned a solution also within the Xposed framework, I'll try that! Sorry, I'm pretty tired haha
Brilliancy said:
I tried searching a bit, but wasn't finding any results for what little I knew. Sorry about that. Thanks a bunch for the help. Will simply disabling S Health solve the issues since I don't use it anyways?
Edit: Just realized you mentioned a solution also within the Xposed framework, I'll try that! Sorry, I'm pretty tired haha
Click to expand...
Click to collapse
hi ,
yes, i think @Zer0r means the XsecureStorage module ( Wanam )
http://repo.xposed.info/module/ma.wanam.xshealth
Just to point out that maybe you overlooked an important fact and that is you still have the lag issue after ........uninstalling Xposed ?
thus Xposed must have "broken" something ? in process ? for you to have lag after uninstalling Xposed ?
to fix you now have to install Xposed again.(thus a temporally fix ????)
When i had Xposed installed and used XsecureStorage module it fixed my Shealthapp ( i had no lag ,so it was not an issue to me ) but it did not fix my Private mode .(So to me its a hit and miss )
Good luck
You can either install the secure storage xposed mod or edit your buildprop and change secure storage to false
willcor said:
When i had Xposed installed and used XsecureStorage module it fixed my Shealthapp ( i had no lag ,so it was not an issue to me ) but it did not fix my Private mode .(So to me its a hit and miss )
Good luck
Click to expand...
Click to collapse
Quote from Wanam's ROM thread:
"If you can't get Private mode to work: backup your user Apps through TB, wipe data partition from recovery, reboot, setup Private mode and restore your Apps."
Zer0r said:
Quote from Wanam's ROM thread:
"If you can't get Private mode to work: backup your user Apps through TB, wipe data partition from recovery, reboot, setup Private mode and restore your Apps."
Click to expand...
Click to collapse
hi,
thank you for your input, but i do know all relevant fixes.. (including your one.) Done them in past. Bottom line
I am not to interested if Private mode works or not..!
The point i am trying to bring across is that Xposed is not 100% optimised
for Note 4 and keeps on breaking various apps!
I have Xposed installed on my Note 3./.Note 2../ Note 8.0 (tab) and my HTC one X, no problems at all on any of these devices! My Note 4 i had Xposed installed on and off, since October this year.. so i do know Xposed very, very well! and relevant patches.
Bottom line is
if the dev. manages to optimise Xposed for lollipop (ART) i will install Xposed again! So i do fancy/like Xposed but is not so hardup to use it, (if it breaks so many apps and you have to patch it.)
This is my message i am try to bring across. with Xposed.. but then its your choice to install or not.?
thanks for your input and good luck
Lesson here is don't use xposed unless u do 5 minutes of reading first on how to use it with this phone. Been using it correctly since launch day, why...... cause I didn't just install it, I read what was suppose to be done before and after it is installed. Sorry just really sick of seeing the countless posts about this. There should be a sticky about xposed, but people would still fail to see it.
Before you even install xposed you should:
1. With titanium backup, freeze health service, private mode, and s health. Wipe data for those apps as well.
2. Edit build prop:
ro.build.selinux to 0 if you have a permissive kernel or want to flash one.
ro.config.knox to 0
ro.config.tima to 0
ro.securestorage.support to false
3. Reboot
4.install xposed, install framework, reboot.
5. Install Wanam 3.2.5,( do Not install newest 3.2.6 as there is something wrong with it, causes reboots while hanging at the startup system update process), go into security hacks and tick disable secure storage, and reboot.
6. In titanium backup, unfreeze health service, private mode, and s health.
7. Reboot and enjoy
I've even done this with skipping some of the reboots and been fine, but just to make sure you have no problems, do everything as written. And yes I know I edit other things in the build prop which is really overkill.
---------- Post added at 12:09 PM ---------- Previous post was at 11:32 AM ----------
willcor said:
hi,
thank you for your input, but i do know all relevant fixes.. (including your one.) Done them in past. Bottom line
I am not to interested if Private mode works or not..!
The point i am trying to bring across is that Xposed is not 100% optimised
for Note 4 and keeps on breaking various apps!
I have Xposed installed on my Note 3./.Note 2../ Note 8.0 (tab) and my HTC one X, no problems at all on any of these devices! My Note 4 i had Xposed installed on and off, since October this year.. so i do know Xposed very, very well! and relevant patches.
Bottom line is
if the dev. manages to optimise Xposed for lollipop (ART) i will install Xposed again! So i do fancy/like Xposed but is not so hardup to use it, (if it breaks so many apps and you have to patch it.)
This is my message i am try to bring across. with Xposed.. but then its your choice to install or not.?
thanks for your input and good luck
Click to expand...
Click to collapse
So u uninstalled xposed and are not installing it again because u don't want to do a lil bit of work after a fresh install, despite all the pluses it brings? I find it so useful that I probably won't upgrade to 5.0 until xposed is compatible unless xposed will never be compatible.
.................................................................
So u uninstalled xposed and are not installing it again because u don't want to do a lil bit of work after a fresh install, despite all the pluses it brings? I find it so useful that I probably won't upgrade to 5.0 until xposed is compatible unless xposed will never be compatible.[/QUOTE]
hi
thanks for you input ,
No ,i think maybe you "misinterpret" my last post ?( I did read up and follow correct Guidelines availeable .)
I stated that i know Xposed quite well and have installed Xposed all my other devices ..no problem etc .
On my Note 4 I have installed Xposed "on and off " since October (maybe 3 or 4 times ? i don't really know .)
Overall Xposed work well, no problems ,its just "sooner or later" an app would break !
eg . after using Xposed for a while( week or so )my Play store " broke"..could'nt install and have to apply fixes /patches all over again ( freeze S health / Install Xposed again /clear Shealth data etc etc )
other instant was using Xposed for a while my 'Samsung store " app broke .......!
Had to apply fixes/patches all over again ....!
I had my Private mode working in most of these cases ,but lost interest in hiding apps ..for what ?
I don't keep no "sensitive " stuff etc. on my device ,so don't really have any need for it .
As i am looking more forward to flash "Lollipop" onto my device ,i am not so "interested "
to keep Xposed on my Note 4 .( for every now and then ,for something to break and then apply fixes , after a while that was my experiences .)
Also i believe Xposed is not fully "optimised " for our Note 4 ..as i stated(/reason) , in my previous post above.
So if you chose to have Xposed on your device ,happy with it ,its your choice . (,i have no problem with that )
( i am also overall a " fan/supporter " of Xposed )
its just that my Note 4 is tweaked / running ... very smooth and i have no complaints/issues about... ..battery /lag or anything in paticular .
Good luck
I have unlocked bootloader, TWRP recovery, Xposed installed, and rooted. Installed Android Pay, linked CC.
Then I get a message that software is not compatible and exits. Any work arounds?
CC
I never used it, but was able to get it setup.
You go into the SuperSU app.
Then settings, disable root, reboot.
Setup android pay.
Then reenable root
Seemed to work for me, but never used it to confirm
Sent from my Nexus 6 using Tapatalk
jaben2 said:
I never used it, but was able to get it setup.
You go into the SuperSU app.
Then settings, disable root, reboot.
Setup android pay.
Then reenable root
Seemed to work for me, but never used it to confirm
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This^^ except you don't even need to reboot. Just disable SU, add card in Pay, re-enable SU. I've done it 4 times on 2 separate phones
cc999 said:
I have unlocked bootloader, TWRP recovery, Xposed installed, and rooted. Installed Android Pay, linked CC.
Then I get a message that software is not compatible and exits. Any work arounds?
CC
Click to expand...
Click to collapse
The Xposed app RootCloak seems to also do the trick without needing to mess with anything else.
Bootup said:
This^^ except you don't even need to reboot. Just disable SU, add card in Pay, re-enable SU. I've done it 4 times on 2 separate phones
Click to expand...
Click to collapse
_ranch said:
The Xposed app RootCloak seems to also do the trick without needing to mess with anything else.
Click to expand...
Click to collapse
Since you mentioned 2 separate phones, I just want to add that disabling SuperSU with and without rebooting, as well as trying RootCloak did not allow me to setup a card on my G4.
geoff5093 said:
Since you mentioned 2 separate phones, I just want to add that disabling SuperSU with and without rebooting, as well as trying RootCloak did not allow me to setup a card on my G4.
Click to expand...
Click to collapse
Not that it matters since we all know by now that Android Pay doesn't work on rooted phones but I was able to setup cards on my gf rooted G4. Simply disabling SU (didn't even need reboot) and she was able to add her cards.
Of course, she can't actually use Pay....
Google Security Engineer Explains Issues With Root and Android Pay in the XDA Forums
Once Xposed is installed the security model is broken for card addition.
Xposed and root must be removed to install cards.
Once the cards are added.
Xposed can be re-installed and root reactivated.
You then will need to run an Xposed root cloak.
It does work, but once you add Xposed no new cards.
tech_head said:
Once Xposed is installed the security model is broken for card addition.
Xposed and root must be removed to install cards.
Once the cards are added.
Xposed can be re-installed and root reactivated.
You then will need to run an Xposed root cloak.
It does work, but once you add Xposed no new cards.
Click to expand...
Click to collapse
I wonder if this will eventually be detected and continue the cat and mouse game? Probably so. And there's no telling how the game will change once we're running Marshmellow.
Personally, I intended to go into Marshmellow virgin stock. With Marshmellow's app data backup, I won't need the #1 reason I used to root. Titanium Backup. Otherwise, I'm a fan of vanilla Android with the Moto customizations. So no reason for me to root.
I tried root cloak but don't know what I am supposed to do with it. Can someone please tell me why to do? Do I do anything on the opening page? Or, do I hit the + and look for the app.
People say even when hiding root it was always fail during the transaction.
Sent from my XT1575 using Tapatalk
Darn it. I really want to have wallet tap and pay, but I want to keep root way more. I uninstalled Android Pay and the new Wallet and installed Wallet v8. It appears that tap and pay is functional (for now).
I detached Wallet from Google Play, so it shouldn't get updated without my permission. We'll see how this goes. I'll heck it out at the nearest Home Depot tomorrow.
The best place to test is at McDonald's. Theirs is always working. But Home Depots in my area stopped working with Tap and Pay many months ago.
Sent from my Nexus 10 using Tapatalk
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
sdelcegno said:
People say even when hiding root it was always fail during the transaction.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
That's right. The Google engineer said all the major checks occur during the transaction. So adding cards really means nothing, if you can't use them...
Sent from my Nexus 10 using Tapatalk
Darnell_Chat_TN said:
The best place to test is at McDonald's. Theirs is always working. But Home Depots in my area stopped working with Tap and Pay many months ago.
Click to expand...
Click to collapse
No more Home Depot, eh? That's too bad. I did notice that Whole Foods updated their registers to remove the tap and pay a year or so ago, too. OK, well, I do like the McD fish sandwiches, and there is one a couple of blocks away, so it is pretty easy to check. Thanks for the info.
sdelcegno said:
People say even when hiding root it was always fail during the transaction.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
i have my phone rooted and xposed installed. I was able to add cards w/ root disabled and am able to may purchases w/ root disabled. it DOES check root on purchase so you have to keep it disabled to use AP.
FunkeeC said:
i have my phone rooted and xposed installed. I was able to add cards w/ root disabled and am able to may purchases w/ root disabled. it DOES check root on purchase so you have to keep it disabled to use AP.
Click to expand...
Click to collapse
That seems to fail with others. I wonder if it is store dependant and some are doing something else with security.
Sent from my XT1575 using Tapatalk
sdelcegno said:
That seems to fail with others. I wonder if it is store dependant and some are doing something else with security.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
or dependent on what modules being used perhaps? im only using xposed for apm+ and gravity box. i can tell you ive used at various retailers (macys and a local liquor store being 2) and once i realized i had to have root off for the purchase i have not had an issue.
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
Are you someone who just got their Fire TV rooted and don't know exactly what you can do with it being rooted? Or maybe you haven't rooted yet because you are unsure of what you can do with it rooted? Well hopefully i can shed some light on this with a little guide on things to do, along with some tips and tricks.
First let me get started by saying never forget to make a backup of your Fire TV via TWRP before making changes or tweaks. This is not to freak you out or disparage its just good practice ii have learned in rooting devices. I will cover TWRP later.
One of the best things to come along in the rooting world of android is Xposed installer. In short Xposed is a framework apk that allows users to modify/ customize their devices. This is not done by Xposed Installer per say but the modules that you download with in Xposed installer. So i will show how to install it, how to use and modules that will be beneficial use for Fire TV fyi mouse is need to navigate Xposed.
Xposed installation
1. We need to download the following BusyBox a program that most rooted apps are dependent on here Xposed Installer v3.1.5 here along with Xposed Framework x89 sdk22 arm64 here
2. Install BusyBox however you install side loaded apks. Open BusyBox and click the install button on bottom right. On SU prompt screen grant root access. As you should for root apps you install.
3. Install Xposed Installer, there is no need to open after install because without Xposed Framework installed it doesnt work.
4 Place the Xposed v89 zip onto Fire TV internal or external storage is your choice just remember where so you can point TWRP to it.
5 Reboot into TWRP recovery, choose install, point TWRP to the Xposed zip and on right side of options choose install zip. Let TWRP run its script when it says complete simply reboot and voila Xposed is installed. NOTE it is NORMAL for the first boot to take 10 min after Xposed is installed.
Xposed Tutorial and Modules
Open Xposed installer on be careful screen prompt click box to don't show again and ok. The 3 line icon on top left is menu button. Module option is where you can see and activate modules you install. Download option is where we search for and install modules. After you download a module Fire TV will prompt you to install. Note modules wont work until activated and a reboot.
Modules i find beneficial and know are SAFE are the followingBoot Manager- this allows for you to choose what apps start on boot.
RootCloak- this is designed to hide root app detection. Im assuming it still will hide root but could be wrong worth shot right
Xposed Edge- this is the FUN one that allows a fair share customs tweaks. My fav is remapping of remote buttons ie home button goes to alternative launcher, double tap home opens netflix. Which is great for 3rd party remotes that have a lot of buttons. NOTE There is a pro version as well Note- whenever you make changes in edge you may have to reboot for changes to effect.
DISCLAIMER be careful some modules may cause problems like bootloop and worse so research before you install modules to see if they are compatible
Other Apps
These are apps recommended or useful for rooted devices and for Fire TV useADBLink-allows you connect PC t to Fire TV via adb can install apks, push/pull files, run adb shell.
Easy Fire Tools- Android app that connects to Fire TV via adb can install apps from your android device onto Fire TV, transfer files and other features.
Root Explorer- these apps allow you to manage files but also a way to install side loaded apps, find one that is root friendly so you can access system folders if ever needed.
AdBlocker- we all know why we want one for all my rooted phones always been partial to adaway.
Alternative Home Launcher- who does like Fire TV launcher, really Karen of course you would!
TV App Repo and APK Editor- For those who do use alternative launcher i mention these because TV App Repo allows you to make bookmarks into apks. APK Editor to change the icon and name of TVApp Repo apks because the names and icons are generic.
TWRP
Finally the benefits and how to use TWRP. This allows users to make a backup images of device and ability to restore it when **** goes wrong. You can also do a factory reset.
Backup- after you choose backup from main screen choose select storage and choose storage then click swipe to backup. These can take a while to do seemed like 20 mins or so. Whatever storage you chose will be the default storage until you change it. Note- I have a backup image and its size is 4.5gb so id recommend you need some sort of external storage for these. If there is not enough space backup can not be performed.
Restore- performed same way as backup.
Factory Reset- Just wanted to mention don't forget if you do this and have a backup image on Fire TV internal storage you will lose it.
Hope this helps out
@g422
Thanks for the write up!!!
To be honest, the benefits of rooting appear to be somewhat underwhelming, at least, for the Fire TV. Not a single killer feature/application ...
I do know that it is more convenient to have root than not, but appears to be in pretty subtle ways.
My main use is between SmartYouTubeTV, and Netflix. If I fumble through the Amazon launcher, I am there, and life is good!
Am I missing something?
bibikalka said:
Am I missing something?
Click to expand...
Click to collapse
Yes, you didn't read the OP He gives many examples of use for root, if those aren't valuable to you, then root isn't for you.
ldeveraux said:
Yes, you didn't read the OP He gives many examples of use for root, if those aren't valuable to you, then root isn't for you.
Click to expand...
Click to collapse
Hmm, just for the record, pretty much every tablet or phone (except a couple of real cheap deals) I have in my household are rooted! So I do see good value in root on those devices.
It's just that I struggle with root utility on Fire TV devices. As in - "why bother?"
I see that the OP likes Xposed Edge for button remapping, so if that's your cup of tea, that's a killer feature to get root for. I myself religiously correct Chrome look on tablets using Xposed/App Settings (link), which very few others seem to care about. But I want to see more of these killer features for Fire TV! Suggestions?
Btw, I am not being adversarial or critical, just very curious. Which itch are people scratching with root on Fire TV???
bibikalka said:
Hmm, just for the record, pretty much every tablet or phone (except a couple of real cheap deals) I have in my household are rooted! So I do see good value in root on those devices.
It's just that I struggle with root utility on Fire TV devices. As in - "why bother?"
I see that the OP likes Xposed Edge for button remapping, so if that's your cup of tea, that's a killer feature to get root for. I myself religiously correct Chrome look on tablets using Xposed/App Settings (link), which very few others seem to care about. But I want to see more of these killer features for Fire TV! Suggestions?
Btw, I am not being adversarial or critical, just very curious. Which itch are people scratching with root on Fire TV???
Click to expand...
Click to collapse
I sort of see your point, but I think the root version of Mouse Toggle works, while the non-root doesn't. At least that's been my experience. Also, can you block updates without root?
I took no offense to your comments bibikalka. I am inclined to agree that there is a limit of what to do with rooted fire tv especially compared to a phone or tablet. I started this thread to give back to xda who has kept my multiple devices over years rooted. Thread was also done in hopes of getting ideas to do and/or sharing of apps that can be helpful especially now that rooting is allowed for the general masses just not those who were able to jump on board early.
ldeveraux said:
I sort of see your point, but I think the root version of Mouse Toggle works, while the non-root doesn't. At least that's been my experience. Also, can you block updates without root?
Click to expand...
Click to collapse
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
#1 reason I root a fire TV box is so I can use large NTFS drives on the USB port.
Can someone point to me how to fix sd card write permissions. I tried xiinternalsd for xposed but when i open it goes to amazon home screen
g422 said:
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
Click to expand...
Click to collapse
Right, so blocking updates only when rooted.
ldeveraux said:
Right, so blocking updates only when rooted.
Click to expand...
Click to collapse
yeah i just re read what ya posted i see what ya meant
Imho top reasons for it are Xposed Edge Pro, ad blocking via AdAway (if you use the browser) and finally, the updates issue. While unlikely, it's not impossible for Amazon to get crackin and stop the use of certain third-party apps (NIMH is a giveaway)
Edit: forgot one important one, "debloating" the OS, whether by blocking the startup or disabling packages you don't want/need to give more cpu and memory to apps you do
Without root access, it's Amazon's device; with root access, it's now your device.
g422 said:
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
Click to expand...
Click to collapse
ldeveraux said:
Right, so blocking updates only when rooted.
Click to expand...
Click to collapse
g422 said:
yeah i just re read what ya posted i see what ya meant
Click to expand...
Click to collapse
For a while, updates could be blocked without root, but Amazon fixed that hole:
https://forum.xda-developers.com/fire-tv/general/disable-ota-fire-stick-t3667978
But! You want to block updates so you don't lose root, so it's a bit circular. If you don't have root, you don't care, and just update as per Amazon otas. Btw, I do have updates blocked on my fire sticks
Anyway, please keep the conversation going! We should develop a good set of must have features which are only available via root.
The main reason I root now is to debloat. Go as barebones as possible in order to improve performance. I kill all possible services that are absolutely unnecessary. I've removed Amazons GUI and use Appstarter. I just like a clean fast experience.
Thanks for this but u all do know u can connect to a PC wirelessly via adb without root. It's the only way I have ever added apps to my stick. Find your sticks individual ip. Open terminal on a pc, adb connect ipaddress. Then adb devices, a prompt will pop like on your phone asking to allow device or not. Click always or yes whatever. Then u do adb install draganddropwhateverapphere. Loads up in seconds depending on apk size. U can even use your phone if u have the adb platform tools magisk module installed on your phone. I install apps to my stick from my OnePlus 6t
fullofhell said:
Thanks for this but u all do know u can connect to a PC wirelessly via adb without root. It's the only way I have ever added apps to my stick. Find your sticks individual ip. Open terminal on a pc, adb connect ipaddress. Then adb devices, a prompt will pop like on your phone asking to allow device or not. Click always or yes whatever. Then u do adb install draganddropwhateverapphere. Loads up in seconds depending on apk size. U can even use your phone if u have the adb platform tools magisk module installed on your phone. I install apps to my stick from my OnePlus 6t
Click to expand...
Click to collapse
Ummm, or you know just use the Apps2Fire app lol. No magisk module or root needed. You're welcome.
JUSTINMARMER said:
Ummm, or you know just use the Apps2Fire app lol. No magisk module or root needed. You're welcome.
Click to expand...
Click to collapse
I am saying I never need root or anything to use adb and install apps wirelessly. I have done this for the past year with NO ROOT. Don't need it for sideloading apps. Adb connect ipaddress, then adb install dragdropapp from PC into terminal. No root or magisk needed. I always have a rooted phone and that's where the magisk module comes in. On a PC u can load them to a stick out of the box.
fullofhell said:
I am saying I never need root or anything to use adb and install apps wirelessly. I have done this for the past year with NO ROOT. Don't need it for sideloading apps. Adb connect ipaddress, then adb install dragdropapp from PC into terminal. No root or magisk needed. I always have a rooted phone and that's where the magisk module comes in. On a PC u can load them to a stick out of the box.
Click to expand...
Click to collapse
Yep, that's exactly what you said before. Not sure why you are repeating it.
JUSTINMARMER said:
Yep, that's exactly what you said before. Not sure why you are repeating it.
Click to expand...
Click to collapse
Cuz u aren't understanding. If u read your comments, then mine, you would see it seems u think I'm saying one would have to have root to use adb install. U do not.
fullofhell said:
Cuz u aren't understanding. If u read your comments, then mine, you would see it seems u think I'm saying one would have to have root to use adb install. U do not.
Click to expand...
Click to collapse
That is 100% incorrect. I see now you have a reading comprehension disability. I can't imagine how hard that must be for you and I empathize.
Obviously root is needed for magisk modules. I suggested an app to help all those without root.
Bless your heart.