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
Related
This is an Xposed module (See http://forum.xda-developers.com/showthread.php?t=1574401 for more on Xposed) that allows disables region/device checks for Google Wallet r87 and above.
Source code for the module is at https://github.com/Entropy512/XposedWalletPatcher
To install:
Install the Xposed Installer APK from the thread linked above
Install the Xposed framework using Xposed Installer
Install the APK linked in this post
Reboot your device after enabling the module in Xposed Installer
Install Google Wallet from the Play Store - No more need for hacked APKs for a banking app. Complete source code for the module showing every method that is patched is provided above.
This will work even if Google Wallet gets updated through the Play Store, as long as method names used for checking don't change. (GW had major changes between r81 and r87 that required changing Xposed modules, however, no changes were necessary from r87 to the current Play Store version.)
NOTE: Initial setup of Google Wallet still requires a hacked build.prop, but you can restore build.prop once you've set it up. Thanks go to ogdobber for most of these settings from http://forum.xda-developers.com/showthread.php?t=1769083
Here are the modified values I use. SAVE YOUR build.prop before editing!!!
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.product.brand=Samsung
ro.product.manufacturer=Samsung
You'll see two differences here from ogdobber's settings: setting brand and manufacturer to Samsung. The reason for this is that his tutorial is for a Galaxy S III - e.g. faking out one Samsung product on a different Samsung product. On my Xperia T, I needed one or both of these additional changes (I have not yet had time to determine which one.)
Many of the tips and tricks in http://forum.xda-developers.com/showthread.php?t=1769083 are still valid - the only difference is you no longer have to install smali-hacked Wallet versions to /system, full source of the module is provided, AND you can update Wallet from the Play Store and it will continue working as long as the compatibility check methods/classes don't change names.
Change Log
Initial Release so far...
Technical Details and other observations
Reserved for Future Use
FAQ
Q: Why does this still require build.prop changes when initially setting up Wallet?
A: For unknown reasons, SOMETHING is directly parsing build.prop and sending it to a server somewhere during initial setup. I have not figured out what is doing it and how to fake it out with Xposed yet.
Q: If I need build.prop hacks, what's the point of this module?
A: Once you have initialized Google Wallet and set up a card, you can return build.prop to its normal state. If you do this without the module, Google Wallet will stop working.
Q: Resetting Google Wallet hangs with at N-3/N steps complete (e.g. 74/77)
A: Resetting GW also needs modified build.prop. DO NOT FEAR: You can safely modify build.prop and reboot even after reset has started. I have done this numerous times.
Confirmed Working Devices/Firmwares
Confirmed Working - build.prop hacks only for card setup/reset
Sony Xperia T
CyanogenMod 10
Sony Xperia Z
.350 Stock
CyanogenMod 10.1
Samsung Galaxy S3 (AT&T - SGH-I747)
CyanogenMod 10.1
Samsung Note 2 (Verizon - SCH-I605)
"Jedi XV13" - Not sure if this really belongs in the "hacked NFC libraries" or is an AOSP derivative.
Working - Requires hacked NFC libraries
TBD
Not Working
Samsung Galaxy S II (AT&T version, SGH-I777) - No Secure Element present
Non-Sprint HTC One units - Unknown, Wallet hangs on setup no matter what anyone does
Oppo Find5 - Same issue as the HTC One
Using the Wallet R96 apk, I was able to install and setup without modification to build.prop on my Sprint Galaxy Note 2, LJC firmware.
Note: The R96 apk will install on my GN2 without this mod, if I use the latest MA7 firmware.
Edit: Google Wallet R96 apk
Sent from my SPH-L900 using Tapatalk 2
on a tmobile sgs2 I get stuck at setting up... I don't know off hand and I'm no at my desktop but I imagine the 989 also doesn't have the secure enabled.
Sent from my Galaxy Nexus using Tapatalk 2
k3v0 said:
Using the Wallet R96 apk, I was able to install and setup without modification to build.prop on my Sprint Galaxy Note 2, LJC firmware.
Note: The R96 apk will install on my GN2 without this mod, if I use the latest MA7 firmware.
Edit: Google Wallet R96 apk
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Doesn't surprise me since Sprint is the only carrier I'm aware of that cooperates with Google - many Sprint phones are officially supported by GW.
iamanalog said:
on a tmobile sgs2 I get stuck at setting up... I don't know off hand and I'm no at my desktop but I imagine the 989 also doesn't have the secure enabled.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I know none of the Exynos-based GS2s had an SE. Don't know about the Qcom variants.
If your NFC gets totally hosed when GW is installed, but then starts working perfectly as soon as you uninstall GW, that's a sign you're missing the SE.
Works on ATT Galaxy S 3 (i747) running CM 10.1 nightlies.
Temporarily made the build.prop edits for initial setup. Just re-install xposed hooks after flashing each nightly.
Thanks dude! I was tired of resetting my build.prop everytime I reboot my phone. :thumbup:
SeNT FRoM oVeR THeRe----->
Just curious, Im on a tmobile sgs3. I used the wallet installer to install wallet perfectly, the version that installs allows you to revert the build.prop changes afther the initial setup and it will still work perfectly. There is a version in the play store though and it prompts me to update. Once I update it says that it will not work with a rooted device. Will this module fix that issue and allow me to update? As of right now, I just unlinked it from the play store using rom toolbox so I dont even see the update anymore.
tp2215 said:
Just curious, Im on a tmobile sgs3. I used the wallet installer to install wallet perfectly, the version that installs allows you to revert the build.prop changes afther the initial setup and it will still work perfectly. There is a version in the play store though and it prompts me to update. Once I update it says that it will not work with a rooted device. Will this module fix that issue and allow me to update? As of right now, I just unlinked it from the play store using rom toolbox so I dont even see the update anymore.
Click to expand...
Click to collapse
It completely removed the root check because when I was using the Galaxy Nexus information in the build.prop file, every time I used wallet it says unsupported device but after I installed the module that unsupported device message went away and I was able to revert my build.prop file back to the note 2 with no issues whatsoever (and I'm on the latest version of google wallet)
On Xperia S i can install but it always says to exit and try again after restarting the device...
Sent from my Nexus 7 using xda app-developers app
This worked perfectly on my VZW Note 2.
Thanks!
Will not get past setting up for purchases note 2 n7100
Sent from my Galaxy Nexus using Tapatalk 2
Sir - Lancelot
Are you running stock rooted or a ROM on you VZW note 2?
Sent from my SCH-I605 using xda premium
areayetee said:
Sir - Lancelot
Are you running stock rooted or a ROM on you VZW note 2?
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Hi.
I am on Jedi XV13. It has the exposed framework installer in the jedi rom tricks. So I just added this module then changed my build prop in rom toolbox pro.
Now I guess I should clarify worked perfectly. lol
I set up wallet when i made that post bit as of today I have not used it. It did however pull all my old cc info from my nexus and seems to be good to go.
I will get gas, a milkshake, or something to see if it does work tomorrow. I see no reason it shouldnt through.
tp2215 said:
Just curious, Im on a tmobile sgs3. I used the wallet installer to install wallet perfectly, the version that installs allows you to revert the build.prop changes afther the initial setup and it will still work perfectly. There is a version in the play store though and it prompts me to update. Once I update it says that it will not work with a rooted device. Will this module fix that issue and allow me to update? As of right now, I just unlinked it from the play store using rom toolbox so I dont even see the update anymore.
Click to expand...
Click to collapse
Yes - with this module, you can update from the market and it will USUALLY work unless Google changed method names.
They did that a few versions ago, but the past 2-3 Play Store updates have not required module changes. If they do I'll probably notice within a day or two and update the module.
dingokevin said:
Will not get past setting up for purchases note 2 n7100
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Need more details. Also refer to the thread that I linked - it has a LOT of useful info on various gotchas, the main difference being that this does not require putting a hacked APK into /system AND, as stated above, often (but not always) continues working after updating via the Play Store.
If you look at some of the other threads, sometimes other hacks are needed other than the hacked APK. This approach ONLY replaces the hacked APK, and not other things that may be necessary, such as hacked up NFC libraries on some devices.
Entropy512 said:
Yes - with this module, you can update from the market and it will USUALLY work unless Google changed method names.
They did that a few versions ago, but the past 2-3 Play Store updates have not required module changes. If they do I'll probably notice within a day or two and update the module.
Need more details. Also refer to the thread that I linked - it has a LOT of useful info on various gotchas, the main difference being that this does not require putting a hacked APK into /system AND, as stated above, often (but not always) continues working after updating via the Play Store.
If you look at some of the other threads, sometimes other hacks are needed other than the hacked APK. This approach ONLY replaces the hacked APK, and not other things that may be necessary, such as hacked up NFC libraries on some devices.
Click to expand...
Click to collapse
Tried that.. copied libs from Sprint GS3 which is known to work and nfc_access.xml certs and what not.. samething... you would NOT be able to pass setting up the payments. Always get Device setup failed.. Gave up on this.. Damn it google..
I have installed the exposed frame work and module, edited build prop like it says in first post. installed Google wallet Apk, but all im getting is
wallets unable to proceed until this device is fully initialized. Make sure the devices has network access and try rebooting if problem persists.
I can't get past this any ideas? I'm on jb stock Xperia s. In settings there is Google wallet or operator Wallet, what is operator wallet for? Thanks
Sent from my LT26i using xda premium
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!
.
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
Hi Guys,
i cannot seems to install Gapps, its just keep asking permission in chinese which obviously i don't understand, can anybody point me to right direction?, anyone have a full Gapps apk for manual install, it seem i can't install Gapps using Google installer
spiderclan said:
Hi Guys,
i cannot seems to install Gapps, its just keep asking permission in chinese which obviously i don't understand, can anybody point me to right direction?, anyone have a full Gapps apk for manual install, it seem i can't install Gapps using Google installer
Click to expand...
Click to collapse
It's pretty straightforward, there are several apps that do this. You can search in Baidu.com for Gapps and the apk will show up. Install it, press the big button and there you go. You can also find several tutorials in Youtube, if you don't know how the app looks like.
Alternatively, here's another tutorial with a different app: http://en.miui.com/thread-17910-1-1.html
somehow i'm able to install Gapps using the installer, i don't know what i did to fix it, anyway its all good now, btw the link you gave is for device that is not bootloader locked
The minimum set of Gapps are very easy to install with the help of this tiny online installer. It's in Chinese, but it's intuitive.
ViAlexSt said:
The minimum set of Gapps are very easy to install with the help of this tiny online installer. It's in Chinese, but it's intuitive.
Click to expand...
Click to collapse
This is the tools that i was using when trying to install Gapps, and after countless of failed effort, somehow it works on its own, i don't know what happened
For me NewGoogleInstaller works flawlessly on all firmwares, including the latest 7.2.4.
yeah, but now i'd like to know how can i set google playstore as a default app store instead of Mi app store
Everything is installed following the process but I can't download any apps from the app store..
rocketfans14 said:
Everything is installed following the process but I can't download any apps from the app store..
Click to expand...
Click to collapse
You must update Google services
And Google Play at the same time.
ViAlexSt said:
You must update Google services
And Google Play at the same time.
Click to expand...
Click to collapse
I did. Well, not exactly the 'same time' but I have updated them..Now, play store is just stuck at a loading circle screen.
rocketfans14 said:
I did. Well, not exactly the 'same time' but I have updated them..Now, play store is just stuck at a loading circle screen.
Click to expand...
Click to collapse
Reboot your phone.
"At the same time" means can be done, but not necessarily.
rocketfans14 said:
Everything is installed following the process but I can't download any apps from the app store..
Click to expand...
Click to collapse
Same here first time, but removed Google*, installed them again and it started working. I rebooted after Google login, Xunlei engine was disabled and download limit set to Unlimited.
it seem that after you login to playstore, you need to wait for a while for it to sync in order for you to be able to download apps, otherwise you'll get unable to contact server error message
ViAlexSt said:
Reboot your phone.
"At the same time" means can be done, but not necessarily.
Click to expand...
Click to collapse
Gotcha. Rebooting didn't change anything at first but I just kept rebooting (..a lot) and it seems to work now.
---------- Post added at 01:45 AM ---------- Previous post was at 01:44 AM ----------
P.Kosunen said:
Same here first time, but removed Google*, installed them again and it started working. I rebooted after Google login, Xunlei engine was disabled and download limit set to Unlimited.
Click to expand...
Click to collapse
I can't find Xunlei engine.. But rebooting (numerous times) seems to work now.. Just hope it stays that way...
Xunlei engine is in Downloads apps settings.
spiderclan said:
Hi Guys,
i cannot seems to install Gapps, its just keep asking permission in chinese which obviously i don't understand, can anybody point me to right direction?, anyone have a full Gapps apk for manual install, it seem i can't install Gapps using Google installer
Click to expand...
Click to collapse
the google installer worked to install the apps but they couldn't establish a connection to the servers. I had to restore my playstore and google apps from a titanium backup file I had and then it would work. So anyone not able to get on google apps try installing old titanium backups, it may work.
One thing to note with all of these is sometimes it just needs time.
After all, the play services and framework often have to register with Google and also update themselves (you're not guaranteed to get the most up to date version for each even with the installer).
I installed mine and they registered fine. But as soon as I tried to download an app from the play store I got weird errors.
Left it a day and boom, worked fine.
I was debating on whether or not this was a device-specific issue or just snapchat being a poopy app, but I think I saw Giga mention this in the thread about Tigerhoods' TWRP backup so I'm inclined to believe this is a z3v-specific issue.
Well, either way, I can't get past login on Snapchat, on my rooted 5.1.1 z3v. Did the whole nine yards-- un/reinstall, remove app data, even went so far as factory resetting, all to no avail. Password is correct cause I've reset it to something I remember... Anyone know why this could be happening, and is there a fix for it? Thanks in advance.
(I'm running Tigerhoods' flashable, haven't gone up to the build with the messages fix yet. If that fixes it, I'm about to look like a massive dummy... But it wouldn't hurt to be sure, right?)
It's a security thing with Snapchat, the same with how Android Pay doesn't work. If it involves money, then the devs don't want the risk of rooting to be an issue for customers in having some hacking crisis.
I don't even know why Snapchat went that way, but I haven't been able to use Snapchat for months. It's also backwards too being an issue on the Z3v since my brother's HTC One M8 is rooted and bootloader unlocked, but can use Snapchat perfectly fine.
Do you have xposed installed? If so uninstall it then login to snapchat. Reinstall xposed..
snootched said:
Do you have xposed installed? If so uninstall it then login to snapchat. Reinstall xposed..
Click to expand...
Click to collapse
Just the installer or the whole framework itself?
I'd like to make sure this actually works instead of being just a throwaway answer because reinstalling xposed to no avail would be really aggravating considering what I've done to try and fix this so far...
Sent from my D6708 using XDA Free mobile app
shinkins said:
Just the installer or the whole framework itself?
I'd like to make sure this actually works instead of being just a throwaway answer because reinstalling xposed to no avail would be really aggravating considering what I've done to try and fix this so far...
Sent from my D6708 using XDA Free mobile app
Click to expand...
Click to collapse
Just use the zip to uninstall the framework in recovery, wipe cache, reboot, install snapchat, login. Once you are logged in you can go back into recovery and flash xposed framework. You don't have to remove any of your apps for xposed. It worked for me. It also worked with android pay.
snootched said:
Just use the zip to uninstall the framework in recovery, wipe cache, reboot, install snapchat, login. Once you are logged in you can go back into recovery and flash xposed framework. You don't have to remove any of your apps for xposed. It worked for me. It also worked with android pay.
Click to expand...
Click to collapse
It wasn't quite as effective for Android Pay but it did work for Snapchat. Thanks a ton!
Sent from my D6708 using XDA Free mobile app
shinkins said:
it wasn't quite as effective for android pay but it did work for snapchat. Thanks a ton!
Sent from my d6708 using xda free mobile app
Click to expand...
Click to collapse
No problem
The problem is actually about google play services. If you disable the permissions of google play services app, snapchat won't work.
Sounds simple, and it probably is, but could someone walk me through the uninstallation process? The "uninstall" button in the app is gray (can't click it) and I can't find the zip mentioned.
Also, would all of this have something to do why the snapchat beta can't be accessed?
TracerBullitt said:
Sounds simple, and it probably is, but could someone walk me through the uninstallation process? The "uninstall" button in the app is gray (can't click it) and I can't find the zip mentioned.
Also, would all of this have something to do why the snapchat beta can't be accessed?
Click to expand...
Click to collapse
Get the appropriate unistaller zip from here
Flash it, wipe cache & dalvik, reboot, login to SC, once logged in, reboot back to recovery and flash xposed framework zip again, wipe cache & dalvik, reboot.
Everything should be fine.
Remember, if you log out from SC , you'll have to do all this again.
Its Xposed. It wont let you login if you have it. You need to uninstall xposed framework and installer and then install snapchat and login. Then just make a titanium backup. If you switch ROMs, you can just install it without any issues.
Also what worked for me is to take a backup of Snapchat in Titanium Backup with it's data (when you're logged in) and then when you restore from TB with data on a rooted phone and/or with xposed you should be logged in when you open it. Not sure if they will work this out, but has worked for me for a while (didn't even realise Snapchat had blocked xposed and root for months after they did it because of this).
So avoids all this uninstall / reinstall of xposed and saves you time
I did the same technique with android pay, but yea, no dice. Has anyone else been able to get this feature back? Kinda ironic with the 2gb deal Verizon has going right now...
Sent from my D6708 using Tapatalk
I followed the uninstall xposed and login then reinstall method. I also use rootcloak which I tried before uninstalling xposed. It worked for me.
Sent from my D6708 using XDA-Developers mobile app