So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
I've tried disabling root via SuperSU, clearing all data for Android Pay and Google Play Services, and resetting my DPI back to 640. None of those did the trick. I'm tempted to try flashing back to 12B and updating to 24B, installing Android Pay and adding my cards, then rooting and restoring a backup.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
Where did you get the play services update?
Are you rooted? It will not run without an xposed module to hide root.
tech_head said:
Where did you get the play services update?
Are you rooted? It will not run without an xposed module to hide root.
Click to expand...
Click to collapse
It should be this one, http://www.apkmirror.com/apk/google...ices-8-1-14-2244331-230-android-apk-download/ and yes I am rooted and I already tried the root cloak exposed module but it didn't work.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
Chilidog said:
It should be this one, http://www.apkmirror.com/apk/google...ices-8-1-14-2244331-230-android-apk-download/ and yes I am rooted and I already tried the root cloak exposed module but it didn't work.
Click to expand...
Click to collapse
Same issue.
Possibly of interest:
http://forum.xda-developers.com/showthread.php?p=62819708
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
roirraW "edor" ehT said:
Possibly of interest:
http://forum.xda-developers.com/showthread.php?p=62819708
Click to expand...
Click to collapse
I may have a build prop file. Somebody will figure it out.
joshua70448 said:
I've tried disabling root via SuperSU, clearing all data for Android Pay and Google Play Services, and resetting my DPI back to 640. None of those did the trick. I'm tempted to try flashing back to 12B and updating to 24B, installing Android Pay and adding my cards, then rooting and restoring a backup.
Click to expand...
Click to collapse
Android pay won't work if you're rooted or if you are using a third party lockscreen.
vv1914 said:
Android pay won't work if you're rooted or if you are using a third party lockscreen.
Click to expand...
Click to collapse
Actually it will work if rooted. There is a root cloak that works. There are people with root running Android Pay.
Something in the build.prop in non-factory ROMs is causing the failure.
I'm trying to get a copy of a factory build.prop for 24b so I can take a look at the differences between it and Jasmine 8.0.
A third party lockscreen is a no go.
tech_head said:
Actually it will work if rooted. There is a root cloak that works. There are people with root running Android Pay.
Something in the build.prop in non-factory ROMs is causing the failure.
I'm trying to get a copy of a factory build.prop for 24b so I can take a look at the differences between it and Jasmine 8.0.
A third party lockscreen is a no go.
Click to expand...
Click to collapse
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
tech_head said:
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
Click to expand...
Click to collapse
Well, I guess I've got something new to try.
I don't know why I'm so obsessed with trying to get Android Pay running. Perhaps because I used to use Wallet before they locked it down for root users, and I missed the memo when they opened it up for rooted phones. I've tried using rootcloak and nodevicecheck. I've tried turning off root with SuperSU. I've tried clearing Android Play Services data (which then forced me to factory reset my watch). I tried setting the DPI back to 640. Same evil message everytime. Cannot be verified.
If this doesn't work, I'll probably give up for a while and wait for a fix. Preferably with a Xposed mod that removes the lockscreen restrictions. Unless I get antsy enough to do a Nandroid backup, flash a 23c KDZ, add the cards, root and restore the backup.
Bramton1 said:
Well, I guess I've got something new to try.
I don't know why I'm so obsessed with trying to get Android Pay running. Perhaps because I used to use Wallet before they locked it down for root users, and I missed the memo when they opened it up for rooted phones. I've tried using rootcloak and nodevicecheck. I've tried turning off root with SuperSU. I've tried clearing Android Play Services data (which then forced me to factory reset my watch). I tried setting the DPI back to 640. Same evil message everytime. Cannot be verified.
If this doesn't work, I'll probably give up for a while and wait for a fix. Preferably with a Xposed mod that removes the lockscreen restrictions. Unless I get antsy enough to do a Nandroid backup, flash a 23c KDZ, add the cards, root and restore the backup.
Click to expand...
Click to collapse
Well, that didn't work. New approach, same message.
I wish there was a way we could consolidate our experiences across all devices. It would be helpful to know which devices and ROMs have more success than others. For example, my observation has been that stock ROMs are more successful than custom ROMS like CM 12.
tech_head said:
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
Click to expand...
Click to collapse
I tried to add cards before I installed Xposed, even after disabling root via SuperSU it wouldn't work.
I managed to add cards by doing the following (on JasmineROM 8.0), all of which are REQUIRED:
1. Set DPI to stock 640
2. Disable SU
3. Reboot into recovery, flash the Xposed uninstaller.
NedDasty said:
I managed to add cards by doing the following (on JasmineROM 8.0), all of which are REQUIRED:
1. Set DPI to stock 640
2. Disable SU
3. Reboot into recovery, flash the Xposed uninstaller.
Click to expand...
Click to collapse
Tried those running RR. Failed again. Seeing that JasmineROM is a stock rom and RR is a CM-based rom, it supports my beliefe that Android Pay doesn't like CM.
I got it to work. Jasmine ROM 8.0.
1. Opened SuperSU app and unchecked "Enable Superuser" box on the Settings tab,
2. Rebooted,
3. Opened Android Pay app and went through the steps to add my Credit Card,
4. Opened SuperSU app and checked "Enable Superuser" box,
5. Rebooted,
6. PROFIT!!!
I do not have xposed installed, so my guess is that xposed may be the problem.
FWIW, I use Tasker and I have a Profile that when I open the Android Pay app, Tasker turns NFC on, and when I close Android Pay, NFC turns off. That works seemlessly. Only issue is that the delay in turning NFC on is a little longer than what Android Pay needs to see NFC, so I get a settings message from Pay. No biggie, I just dismiss it because by the time the message comes up, NFC has already been turned on.
I too can confirm Android Pay works on JasmineROM 8!
If I've helped, please don't forget to press the “Thanks” button!?
I read somewhere that it checks the bootloader. I have the "1003" secure boot error and I can't add cards no matter what I do regarding SU. Is this a common thread with everyone here that can't verify? Anyone know how to correct it while running CM12?
csyrell said:
I got it to work. Jasmine ROM 8.0.
1. Opened SuperSU app and unchecked "Enable Superuser" box on the Settings tab,
2. Rebooted,
3. Opened Android Pay app and went through the steps to add my Credit Card,
4. Opened SuperSU app and checked "Enable Superuser" box,
5. Rebooted,
6. PROFIT!!!
I do not have xposed installed, so my guess is that xposed may be the problem.
FWIW, I use Tasker and I have a Profile that when I open the Android Pay app, Tasker turns NFC on, and when I close Android Pay, NFC turns off. That works seemlessly. Only issue is that the delay in turning NFC on is a little longer than what Android Pay needs to see NFC, so I get a settings message from Pay. No biggie, I just dismiss it because by the time the message comes up, NFC has already been turned on.
Click to expand...
Click to collapse
I'm running Xposed and a new cloak module developed in the last few weeks for Pay.
I also have Tasker set up to enable NFC on Pay opening.
A modified framework (Xposed), root and a ROM not based on stock all cause issues.
BTW: I'm on Jasmine 8.0.
Considering backing up my current configuration, flashing JasmineROM, adding cards, and then restore the backup.
Sent from my LG-VS985 using XDA Premium App
Related
I installed the hacked Google Wallet from here to work around VZW's restriction. Now a new version is available in the Play Store. Should I wait for the hacked version to be updated here or can I download the update from the store without losing functionality?
Thanks.
Tappin' and talkin' with Tapatalk.
silverfang77 said:
I installed the hacked Google Wallet from here to work around VZW's restriction. Now a new version is available in the Play Store. Should I wait for the hacked version to be updated here or can I download the update from the store without losing functionality?
Thanks.
Tappin' and talkin' with Tapatalk.
Click to expand...
Click to collapse
I would wait, I installed the play version of wallet on my vzw s4 and it tells me that it's not yet available for my network and/or device.
Ok. Will wait. I wonder if we'll have to go through all those steps when we install the updated hacked version.
Thanks.
Tappin' and talkin' with Tapatalk.
denmalley said:
I would wait, I installed the play version of wallet on my vzw s4 and it tells me that it's not yet available for my network and/or device.
Click to expand...
Click to collapse
Are you rooted using the wallet mod that is posted on the forum?
I just installed the update last night and I never saw that.. It even set up tap and pay without issue.
silverfang77 - The latest Google Wallet does work with the xposed addon (my signature lists what I am using for Google Wallet compatibility). All I did was run a script to edit the build.prop, I reset Google Wallet, updated Google Wallet, set up Google Wallet and then ran another script to restore my build.prop
I am not sure if your using a custom recovery or not, but if you are you can always do a nandroid backup in case if there is a problem.
Sorry, I guess I didn't quite understand. I thought the OP was asking if the play store version had opened up the functionality. I do not know if installing on top of a hacked version would work or not. I am rooted, but I installed wallet fresh from play without any prior mods or installs.
im using the new wallet with no mod from play store and it worked
Sent from my SCH-I545 using Tapatalk 4
ogrekane313 said:
im using the new wallet with no mod from play store and it worked
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
You actually performed a touch to pay transaction? Most don't give a hoot about the new features if you have to give up NFC transactions. And FWIW, even if the app says tap to pay is active, many are reporting failures when actually trying to use it.
not yet ill report back .
Sent from my SCH-I545 using Tapatalk 4
http://forum.xda-developers.com/showthread.php?t=2303325 I have the workaround running on my S4 if you want to give it a go. Open1your1eyes0 has it figured out. I was able to make a tap and pay purchase to confirm it. Only catch is you have to be on a TW ROM.
Sent from my SCH-i545 using RedBull & Viagra.
No custom recovery as I foolishly installed the AME7 update before I knew what it was.
So by consensus, it is OK to update Google Wallet from the Play Store as long as I have those special install files and just edit the BUILD.PROP to make it think it's installing on a Nexus?
I would wait to update
Hi,
I would wait to update as they are still working out some bugs if you have a custom rom. If your stock ME7 Rooted then you might go ahead. Thats what I have. It's all setup for tap and pay, I just need to test it.
Good luck,
silverfang77 said:
No custom recovery as I foolishly installed the AME7 update before I knew what it was.
So by consensus, it is OK to update Google Wallet from the Play Store as long as I have those special install files and just edit the BUILD.PROP to make it think it's installing on a Nexus?
Click to expand...
Click to collapse
Well, i installed the version from Play Store, and it worked fine on my un-rooted, stock S4. I even made a purchase at McDonalds with it.
So this new one isn't being blocked by Big Red?
Tappin' and talkin' with Tapatalk.
The app is not, but they're still blocking payments through NFC. It exists as a way to manage your stored credit cards and suchlike.
CrookedKnight said:
The app is not, but they're still blocking payments through NFC. It exists as a way to manage your stored credit cards and suchlike.
Click to expand...
Click to collapse
No, not on my phone. I can make transactions perfectly with NFC.
silverfang77 said:
No custom recovery as I foolishly installed the AME7 update before I knew what it was.
So by consensus, it is OK to update Google Wallet from the Play Store as long as I have those special install files and just edit the BUILD.PROP to make it think it's installing on a Nexus?
Click to expand...
Click to collapse
There are several threads detailing how to get the stock APK to work.
Here is an alternate method using a modded APK by user loserskater:
open1your1eyes0 said:
Try the following:
Force Stop on Wallet app
Clear Cache and Clear Data on Wallet app (in Application manager)
Delete all traces of it from both locations /system/app and /data/app/ (might be called Wallet.apk too)
Reboot
Flash a fresh version of your AOSP-based ROM (no wipe required)
Push the apk from this link to location /system/app/ and set the permissions to rw-r--r-- (DO NOT OPEN IT YET!!)
Reboot
Open the Wallet app and set everything up
Check what Tap and Pay says in "About" section of the app
Confirm what happens on transaction
***Note*** If the ROM your are flashing is TouchWiz-based for step 5 you need to flash one of the below for your device BEFORE step 6 and then continue.
For Galaxy S3: http://forum.xda-developers.com/attachment.php?attachmentid=1943165&d=1367940081
For Galaxy S4: http://forum.xda-developers.com/attachment.php?attachmentid=2006809&d=1370008832
Click to expand...
Click to collapse
This worked perfectly for me when following these instructions exactly.
I can't follow step five as I'm on stock AME7, which cannot be ROMed or have recovery installed. I was able to install Google Wallet by installing the Wallet Installer and Xposed Installer apps, which took over the functions that normally would have been achieved via a custom recovery, via these instructions, omitting steps seven and eight.
Would I be alright just clearing the cache and wiping the data of the current hacked Wallet I have, doing the BUILD.PROP edit I did before and installing that way? I still have the Wallet Installer and Xposed Installer apps installed. Do I need to download the new version of Wallet from the Play Store and then run those two files again?
vt0r said:
There are several threads detailing how to get the stock APK to work.
Here is an alternate method using a modded APK by user loserskater:
This worked perfectly for me when following these instructions exactly.
Click to expand...
Click to collapse
What rom and kernel combo are you running.
Rooted S4
I used Towelroot and KindleFree to root my HDX and install Google apps. I did not disable OTA in KindleFee.
Now when I check for updates, it says "Last updated failed", when I try to set off an alarms off Amazon's site it fails and it doesn't locate the HDX.
I suspect that either Towelroot or KindleFree disabled something, but just to make sure, do they disable something by default that prevents those three things from working? Wanna make sure something else isn't wrong with my device.
well
herzzreh said:
I used Towelroot and KindleFree to root my HDX and install Google apps. I did not disable OTA in KindleFee.
Now when I check for updates, it says "Last updated failed", when I try to set off an alarms off Amazon's site it fails and it doesn't locate the HDX.
I suspect that either Towelroot or KindleFree disabled something, but just to make sure, do they disable something by default that prevents those three things from working? Wanna make sure something else isn't wrong with my device.
Click to expand...
Click to collapse
Well I am guessing if you say you have gapps working that you had to install hdxposed module and framework... If you had read OP of the modification that you installed you would know already that the 1.3 version blocks ota, and probably as a side effect blocks a couple of other Amazon exclusive services .
jimyv said:
Well I am guessing if you say you have gapps working that you had to install hdxposed module and framework... If you had read OP of the modification that you installed you would know already that the 1.3 version blocks ota, and probably as a side effect blocks a couple of other Amazon exclusive services .
Click to expand...
Click to collapse
Yes, I totally forgot that I installed that as well! It's what's doing it. I posted in that thread, but any idea what it does to disable OTA? I tried completely removing it modules, Xposed and ran the script to enable OTA, but it still doesn't work.
herzzreh said:
Yes, I totally forgot that I installed that as well! It's what's doing it. I posted in that thread, but any idea what it does to disable OTA? I tried completely removing it modules, Xposed and ran the script to enable OTA, but it still doesn't work.
Click to expand...
Click to collapse
What is your current system ?
This is a simple app to install GApps and disable items on your Kindle. This was tested on Fire HD 7 4th gen. I do not know the status on HD 6. but in theory it should work just fine. It doesn't make any MAJOR changes to where it would cause a non-booting system.
But with all things in the development world, you are taking a risk. I have tested this about 10 times on my own tablet.
Obviously, you need root for this. The only known way to root is via KingRoot.
The GApps install is a very minimal install to /system that fully works. It is no different than flashing a GApps package in recovery. I am also disabling updates for Play Store and Play Services. The method used is the ones referenced a few times in this forum. I am unable to find the original finder of this information so if you find the original source I will link that content appropriately.
Download Here
The safe way to disable ads on lockscreen and still use profiles or FreeTime is to run this command on every boot. "chmod 000 /data/securedStorageLocation/dtcp/adunits"
Changelog:
v4: Fixed backwards logic in BootReciever to block or unblock ads on boot. Thanks @DoLooper for pointing out the bug
v3: Updated Gapps with combination found by @AlbusAngelus and the casting libs needed he found. Changed the layout to more material design
v2: Found bug with button not showing enabled. Found MAJOR bug with the pm block method of disabling ads on lockscreen. Found workaround
v1: Original Release
jmz said:
This is a simple app to install GApps, busybox, and disable items on your Kindle. This was tested on Fire HD 7 4th gen. I do not know the status on HD 6. but in theory it should work just fine. It doesn't make any MAJOR changes to where it would cause a non-booting system.
But with all things in the development world, you are taking a risk. I have tested this about 10 times on my own tablet.
Obviously, you need root for this. The only known way to root is via KingRoot.
The GApps install is a very minimal install to /system that fully works. It is no different than flashing a GApps package in recovery.
Right this minute I would like a tester or two before releasing publicly. There may be some items left on my device that is causing it to seem to work. I just need someone that has done nothing but root.
Just post here and I will PM you details.
Click to expand...
Click to collapse
I have a fire HD7 just doing root right now
I'd be happy to give it a whirl. My Kindle is just sitting here on my desk right now, may as well do something with it.
jmz said:
This is a simple app to install GApps, busybox, and disable items on your Kindle. This was tested on Fire HD 7 4th gen. I do not know the status on HD 6. but in theory it should work just fine. It doesn't make any MAJOR changes to where it would cause a non-booting system.
...
Right this minute I would like a tester or two before releasing publicly. There may be some items left on my device that is causing it to seem to work. I just need someone that has done nothing but root.
Just post here and I will PM you details.
Click to expand...
Click to collapse
Nice tool! I would test it if I had not done everything manually. With GAPPS, do you block updates to Google Play Services by creating a directory in /data/app in order to keep version 6.0.99 which works?
Tester
Would gladly test this for you. I've rooted my HD 7 using KingRoot
Updated OP
jmz said:
This is a simple app to install GApps and disable items on your Kindle.
Click to expand...
Click to collapse
Thanks for this! Does it install google framework 4.4.4 and a gps that supports latest playstore? Also, can we use it to RE-enable OTA, launcher, ads ? thx
DoLooper said:
Thanks for this! Does it install google framework 4.4.4 and a gps that supports latest playstore? Also, can we use it to RE-enable OTA, launcher, ads ? thx
Click to expand...
Click to collapse
Yes it allows you to renable each of those.
As for the Play Store. The version being installed is 5.5.8. the Google Services Framework is 4.0.4. I am looking into ways to make updates work. There is no reason why updates shouldn't work.
Updated app. Please read the notes about upgrading.
jmz said:
As for the Play Store. The version being installed is 5.5.8. the Google Services Framework is 4.0.4. I am looking into ways to make updates work. There is no reason why updates shouldn't work.
Click to expand...
Click to collapse
Is there a reason you choose Framework 4.0.4 over 4.4.4? Just curious as to why you choose it over 4.4.4, maybe some undesired effect I'm unaware of yet?
AlbusAngelus said:
Is there a reason you choose Framework 4.0.4 over 4.4.4? Just curious as to why you choose it over 4.4.4, maybe some undesired effect I'm unaware of yet?
Click to expand...
Click to collapse
Its the one that I could get working. Using updated ones, I only got white play store with loading screen. Unless you have a combination that works with more updated ones.
jmz said:
Its the one that I could get working. Using updated ones, I only got white play store with loading screen. Unless you have a combination that works with more updated ones.
Click to expand...
Click to collapse
Are you saying with your combo you can let them update and they work?
Framework 4.4.4
Store 5.5.12
Play Services 7.0.99 - 034 --- Edit
Account Manager 4.4.4
This seems to work if you block updates for the store and services. The only issues I'm running into now is chromecast has stopped working correctly, and I had it working fine before root, and after initial root. Once I put playstore on it seemed to stop.
AlbusAngelus said:
Are you saying with your combo you can let them update and they work?
Framework 4.4.4
Store 5.5.12
Play Services 7.0.99 - 036
Account Manager 4.4.4
This seems to work if you block updates for the store and services. The only issues I'm running into now is chromecast has stopped working correctly, and I had it working fine before root, and after initial root. Once I put playstore on it seemed to stop.
Click to expand...
Click to collapse
No they won't update because I disable updating when installing them. I will check chromecast tomorrow and see if it works
jmz said:
No they won't update because I disable updating when installing them. I will check chromecast tomorrow and see if it works
Click to expand...
Click to collapse
Well the setup I listed works okay without the white loading screen. If chrome cast works on the older stuff though I'm going to go ahead and roll it all back and freeze it there. Chrome cast functionality is pretty vital, as my Kindle was basically being used as a movie streamer, before the root break through. Thanks for checking into chrome cast!
AlbusAngelus said:
Well the setup I listed works okay without the white loading screen. If chrome cast works on the older stuff though I'm going to go ahead and roll it all back and freeze it there. Chrome cast functionality is pretty vital, as my Kindle was basically being used as a movie streamer, before the root break through. Thanks for checking into chrome cast!
Click to expand...
Click to collapse
Don't get me wrong. I don't have that white loading issue with my tool. Only if I tried to update past what exists in my tool.
Just something I can think of is download the 4.4 gapps package like you would on AOSP and find the cast lib file and push it to /system/lib and see if that fixes it. I think it is libgcast.so. not 100% on that though. I know for a fact it has cast in the name
jmz said:
Don't get me wrong. I don't have that white loading issue with my tool. Only if I tried to update past what exists in my tool.
Just something I can think of is download the 4.4 gapps package like you would on AOSP and find the cast lib file and push it to /system/lib and see if that fixes it. I think it is libgcast.so. not 100% on that though. I know for a fact it has cast in the name
Click to expand...
Click to collapse
Oh I know , I'm just saying if you are already blocking updates with the tool as might as well go to 4.4.4 and newest playstore, because they are working with now without issue.
(Unless that's what's breaking chromecast) I'll check into the cast file when I get home, I'm at work for another 6 hours.
AlbusAngelus said:
Oh I know , I'm just saying if you are already blocking updates with the tool as might as well go to 4.4.4 and newest playstore, because they are working with now without issue.
(Unless that's what's breaking chromecast) I'll check into the cast file when I get home, I'm at work for another 6 hours.
Click to expand...
Click to collapse
Can you toss me the 4 apks you used?
jmz said:
Can you toss me the 4 apks you used?
Click to expand...
Click to collapse
Absolutely, here they are.
And btw, your chromecast idea worked brilliantly. You could implement the install of those too perhaps? I don't know if everyone is as huge on casting as I am, but that was a lifesaver.
AlbusAngelus said:
Absolutely, here they are.
And btw, your chromecast idea worked brilliantly. You could implement the install of those too perhaps? I don't know if everyone is as huge on casting as I am, but that was a lifesaver.
Click to expand...
Click to collapse
yeah i did. Updated OP
jmz said:
yeah i did. Updated OP
Click to expand...
Click to collapse
Just to confirm, tool now uses framework 4.4.4 and services 7.0.9.6 (or 9.9) and prevents them from updating? Thank you so much!
.
After I root a phone, I would like to be able to uninstall/remove some stock apps (for example, stock Messaging app) and add some new apps (for example, 3d-party Messaging app).
Do I need Titanium app to achieve that? Or is there something more lightweight?
After I complete the setup, I want to disable/ restrict any further software changes. Pretty much the same as Window OS "Admin" VS "Standard User"
So I guess I would need some app manager capable of permission managing.
Any advice on my project? Will my phone be as stable as the original stock after such modding?
The phones: Moto E2 and Moto G2 and G3, Android 5.01 or 6.01
Well, Backing Up the Stock Content before doing any Modding to your Phone is a Good Practice and Extremely Recommended in Case of any worst case scenarios and you can achieve the same by Titanium Back or any Other app Readily available on Play Store.
After Back up, Yes, you can Uninstall PreInstalled apps or any other bloatware that you may don't want in your phone. And Install 3rd Party apps in place of stock Ones.
Talking about Permissions, until/unless you give Root Access to that App, it won't be able to Make any changes in the System. So, you also have to keep a check on giving Root permissions to apps.
Your Phone Will remain stable When you know what actually you are doing with it and what measures could be taken to revert it.
abhinavp649 said:
Talking about Permissions, until/unless you give Root Access to that App, it won't be able to Make a.
Click to expand...
Click to collapse
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
rybshik said:
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
Click to expand...
Click to collapse
You can't restrict to install and uninstall apps. As abhinavp649 said the application makes modifications to the system if you give root permission to them. If you are using SuperSU superuser app then you can set pin to grant root permission to the app from the settings of supersu
rybshik said:
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
Click to expand...
Click to collapse
To Prevent app from uninstalling the best way is to hide it From Home screen Or Make that as System.
And Revoke SU permissions from those apps which can uninstall system apps or any similar one.
Hit thanks if Helped :laugh:
abhinavp649 said:
to hide it From Home screen Or Make that as System.:
Click to expand...
Click to collapse
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
rybshik said:
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
Click to expand...
Click to collapse
Installing an App as system is a easy and you can find tools easily on play store. Just search 'make app system' or something else similar.
Using GPS to prevent Turn off? I think you are expecting too too much out of a device.
However, you can disable Power Off from options you get by holding lock button.
To do this You Have to Install Xposed Framework in your Device.
Xposed Framework allows you to do Amazing modding to your Android device. You can just do everything with the device(Exceptions are always present)
rybshik said:
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
Click to expand...
Click to collapse
If you are thinking of turning on GPS for the sake of tracking your kids, then make sure you tell them you are doing so. Have known a few people that got into legal trouble for not doing so.
In the end if the kids are smart enough there will be nothing you can really do as they can just reset the device and everything you did is gone.
zelendel said:
nothing you can really do as they can just reset the device
Click to expand...
Click to collapse
So, can I prevent that by disabling/removing or password-protecting the option of "Factory Reset" on a rooted Android 6.0?
rybshik said:
So, can I prevent that by disabling/removing or password-protecting the option of "Factory Reset" on a rooted Android 6.0?
Click to expand...
Click to collapse
No. You can not restrict or disable factory data reset option by any ways even you are rooted. Some brands like Samsung gives FRP (factory reset protection) to their device. Devices without FRP easily factory data reset by entering in recovery mode or in settings.
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
nola mike said:
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
Click to expand...
Click to collapse
That's not an issue with Pay. If Magisk was being blocked by root/unlocked bootloader, you would get a message when you first fire up Pay that your phone can't be verified so "Google Pay can't run on this device".
Have you contacted your bank to make sure they support it? If it's not being verified with your bank, sounds like you need to call them. For the last few years, my bank didn't. It wasn't until this past year that they actually allowed it.
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
nola mike said:
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
Click to expand...
Click to collapse
Well that's weird. Glad it's working though! :good:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Sent from my Redmi 4 using Tapatalk
Yes and No
cneeli78 said:
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
Sent from my Redmi 4 using Tapatalk
Click to expand...
Click to collapse
Phone permissions have nothing to do with root features, I didn't exactly understand what do you mean by reuse root features but I don't recall any root solution app or framework asking for Phone Permission. If you are asking about granting phone permission to Google Play Services after Google Pay registration, you should do it, it's not recommended to deny phone permission to Google Play Services. And once you hide Magisk you don't need to change it's state as Magisk will continue to work as expected whether it's hidden or not.
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
Yes it's working
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
thanks.its working
You are welcome
Arokia said:
Yes it's working
Click to expand...
Click to collapse
Karthik Arun said:
thanks.its working
Click to expand...
Click to collapse
There is a thanks button you can press if I could help you
JackFrost said:
There is a thanks button you can press if I could help you
Click to expand...
Click to collapse
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
raguilera510 said:
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
Click to expand...
Click to collapse
Did you by any chance remove phone permission from Google Pay app? You need to turn off telephone permission from Google Play Services and Google Play Store. Google Pay app needs phone permission to verify the phone number, don't turn off phone permission from Pay, do it for only play store and play services. Hope that helped.
Does not work
Once I renable telephone permission for Google Play Services, googlepay does not work anymore. Asks me to register and then I cannot register as I dont pass the security test. I am on lineage os 15.1
Non rooted lineageOS
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
kekekelasomot said:
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
Click to expand...
Click to collapse
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
ChazzMatt said:
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
Click to expand...
Click to collapse
Thank you. Just flash magisk and hide google pay using it. From what i under stand is i have root access+ unlocked bootloader+ google pay functionalities. And the reason not to root is just because i want the feel of stock android+some nice modification
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
AsItLies said:
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
Click to expand...
Click to collapse
Thank you. That's all I had to do to get it working for me.
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Forsh said:
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Click to expand...
Click to collapse
Use Magisk v19. I believe it's a beta at the moment