If anyone is able to help me, I would greatly appreciate it.
I installed Google Wallet (via this APK) when I first got my Verizon LTE GN a few weeks back. I've since used the app daily and it has worked perfectly, up until this evening.
Today, for the first time ever, I decided to unlock my bootloader in order to root my device--all of which went smoothly. I then re-downloaded the above GW APK (since unlocking wiped my device) but now when I launch the application, the screen stays at "Initializing your device - This may take a few minutes depending on your network connection." The application doesn't freeze (the circle continues to spin), but after 30 minutes of waiting, still, nothing has happened. I've tried reinstalling the APK but that does nothing. I have 4G connectivity and have tried over WiFi also.
I am running stock recovery, stock ROM, stock everything on 4.0.2. All I did was unlock the bootloader & root the device. I've done quite a bit of searching but have been unable to find a solution. Does anyone know what may be causing the issue or what I could do to fix it? I really enjoy using the application
I'm having a pretty similar problem.
CDMA Galaxy Nexus.
When I first got the phone, I downloaded the Google Wallet apk and it worked fine. Used it a few times out in the real world.
Today, used the wug unlock/root method, and installed a custom rom.
Though the rom feature log said it contained Google Wallet, it did not.
I redownloaded the original APK that I had used and it installed, but now I get this "Unfortunately wallet has stopped" message every time.
In fact, it comes up on the screen at random intrevals.
Not sure if there's anything I can do.
Do you guys have NFC enabled from the settings menu?
Also, did you try disabling and re-enabling NFC? It's different hardware, but after flashing one ROM I had to disable/re-enable GPS before it would work... worth a shot.
Related
Hi guys,I searched the forums but cant find a a post retaing to the problem im having so I hope this is in the right area. I just rooted my S3 last night had no problems. I installed google wallet following the instructions that are in these forums,I followed them to a T cleared my caches,flashed the 2 files (the apk,and nfc,lib fix) and changed my prop files. Everything installed perfectly,I could add my credit cards and even when I log into google wallet acount online I can see I have a device connected to my account. My problem is when I go to use my pay pass it wont work,I tried it with my phone unlock on the homescreen,I tried it with the google wallet app open. Nothing! I tried 5 different stores today thinking maybe a pay pass terminal was broken but no of them responded. I know my NFC still works because I can still use my tectiles cards. Am I missing something? Or need to flash another file I missed? Any help would be great thanks.
Im on ATT running stock rom with clockworkmod.
You most likely didn't miss anything. It just doesn't work with some of the ota updates..
Do more research but If you can confirm that.. Flash to an older version of 4.0.4..
I'm stock and haven't ran any ota updates and it runs fine.
Sent from my SAMSUNG-SGH-I747 using xda premium
I was running cm-10.2.1 and last night I installed CyanogenMod updates cm-11-20140104-SNAPSHOT-M2 and cm-11-20140210-SNAPSHOT-M3. Several of my apps either quit working or disappeared. When I clicked on Play Store to try and re-install the apps, I got a message of "No Connection". Searched the problem and several people said to delete the Google Account and re-install it. After deleting it, the phone will not let me recreate it. When I click on Add Account and then the Google symbol, nothing happens.
Is there solution to fix this? if not, can I just re-install 10.2.1 and fix it?
My phone is an AT&T SGS3.
Thanks,
retnuh
Re-flash GApps, that has happened to me before, and this is what fixed it.
As LittlePalmTree stated, sounds like you need to reflash GAPPS. Make sure you grab the one compatible with cm11. cm11 is android 4.4 where as cm10.2 was 4.3 if I am not mistaken.
Thanks for the help. I tried to re-flash the gapps after reading the first reply but before reading the second reply. You guessed it. I did it wrong. The phone would not get past the spinning circle screen. Ended up using CWM to re-flashing the rom stored on my phone and also re-flashing the gapps stored on my phone. So, I'm back to version 10.2.0, but at least my phone is working again. While I would like to update, I'm afraid I will mess my phone up again.
Thank you for both of your replies.
Googled the problem and found a few solutions from the simple - force stop/clear cache - up to full factory resets.
Different things seemed to work for different people.
Tried the force stop/clear cache and check time/date is correct (which causes some people problems.
Then I tried removing my Google account and adding it in again. However, it wouldn't let me do that until I re-flashed GAPPS. Did that and it all works fine now.
So last night I flashed dottat's RUU (http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643) to update my phone to 4.4.3 stock. Usually when I run the stock rom, I try to get rid of all the verizon bloat garbage using root app delete and root browser. Maybe this time I got a little overzealous, because I most recently deleted two system apps: verizon location app, and the verizon cloud sync app. Before I did this, everything seemed to run fine. But after getting rid of those two, everything went haywire. Every few seconds my phone app would crash and it would give me the message that "unfortunately, com.android.phone has crashed"and the display kept flickering on and off. Also, I keep getting a poppup for an app called Phone: HBPCG Current Country" telling me I have not input my country, and asks me to select one from a blank list. After trying a few things, I went into TWRP to wipe the cache and dalvik. Fortunately, that seems to have cleared up the com.phone process from crashing every 10 seconds or so. But I still keep getting asked to select a country from "HBPCG Current Country". Has anybody experienced this or does anybody know how to stop it, maybe by deleting another service? I can't remember ever seeing a "verizon location reporting" app in 4.4.2 so I figured it was more garbage that verizon added to the ROM as needless bloat, and didn't think it would affect other phone services.
Thanks for any help on this, it's really irritating me. If I can't get it resolved I figure I might have the run the RUU again.
I should probably also mention that after wiping the caches, I got the "android is upgrading" bit when I rebooted and it said it was optimizing 67 apps. I'm not sure what that was for since I didn't flash any updates or anything, but I figure maybe recaching some system info since I ripped out so much system bloatware?
Now that santod released stock 4.4.3 debloated you should just flash that ROM instead. Sounds like less of a headache to just completely wipe and go from there.
BranC85 said:
So last night I flashed dottat's RUU (http://forum.xda-developers.com/ver...nt/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643) to update my phone to 4.4.3 stock. Usually when I run the stock rom, I try to get rid of all the verizon bloat garbage using root app delete and root browser. Maybe this time I got a little overzealous, because I most recently deleted two system apps: verizon location app, and the verizon cloud sync app. Before I did this, everything seemed to run fine. But after getting rid of those two, everything went haywire. Every few seconds my phone app would crash and it would give me the message that "unfortunately, com.android.phone has crashed"and the display kept flickering on and off. Also, I keep getting a poppup for an app called Phone: HBPCG Current Country" telling me I have not input my country, and asks me to select one from a blank list. After trying a few things, I went into TWRP to wipe the cache and dalvik. Fortunately, that seems to have cleared up the com.phone process from crashing every 10 seconds or so. But I still keep getting asked to select a country from "HBPCG Current Country". Has anybody experienced this or does anybody know how to stop it, maybe by deleting another service? I can't remember ever seeing a "verizon location reporting" app in 4.4.2 so I figured it was more garbage that verizon added to the ROM as needless bloat, and didn't think it would affect other phone services.
Thanks for any help on this, it's really irritating me. If I can't get it resolved I figure I might have the run the RUU again.
Click to expand...
Click to collapse
Verizon Location WAS in fact in 4.4.2, and many services of the phone depend on it and won't function without it…
So I tried doing the systemless root thing. I tried confirming that android pay would still work by removing my cards then attempting to re-add them and it failed. I tried undoing what I did by flashing stock recovery, boot, and system. Still a no-go. I tried running the flash-all.bat (i removed the "-w" so I would keep my data). Still can't add a card.
I resorted to running the flash-all.bat, build MDB08M, to be 100% stock. I STILL CANNOT add a card. The message has been the same every single time "Android Pay cannot be used - Google is unable to verify that your device or the software running on it is Android compatible"
Am I missing something? I don't understand how a 100% stock flash is not able to work.
If it makes you feel any better I've been running 100% stock since day 1 and tried using Android Pay for the first time today. Failed same as yours saying device or software couldn't be verified. I had originally set it up using my card that was already set up on my Google account. When this card didn't work I removed it and tried adding the card again manually. Couldn't even add a card. Tried rebooting several times and disabled developer options. Still not working.
I can select a card already on my google account, accept the terms, then the message pops up. Happens with two different cards associated with my account.
I'm fully stock, but unlocked bootloader.
Android pay used to work as recently as 4 days ago, but failed today with the error unable to verify.
Not willing to relock bootloader. Was there an update of Google play services that changed the way they check for modifications to include bootloader unlock?
I went back to complete stock relocked bootloader and Android paid don't work for me because chase bank stopped supporting Android pay so I went back to custom ROM
Just to note my bootloader is unlocked, otherwise I am 100% stock.
I manually tried updating Google play services to the latest version, but Android Pay gave me the same message but at a different point in the process - right after I clicked "Add a credit or debit card." I wasn't even able to see cards already associated with my account like before. I ended up uninstalling the update because it seemed to make things worse.
I just tried this app and it says I'm failing the SafetyNet check:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Same here. Completely stock 5x with nova. Had added a card, but wasn't working so I deleted it to try to re-add. No luck... Pretty annoying actually. I don't use it that often, but there have been several occasions I forgot my wallet going to the grocery store and paid with android pay cause it's all I had. Hope it gets fixed soon.
Looks like it is working all of a sudden. I was trying the safetynet checking app a few times a day... just tried now and it finally passed. Gave android pay a whirl and both cards were able to be added without issue. So apparently something happened on Google's end. Google play services is the same version now as it was when android pay failed to work.
I was failing the safetynet API yesterday. I still am.
I was also unable to pay with anything yesterday, but today I was able to add a card. Presumably it's partially fixed.
I went completely stock with relocked bootloader and STILL failed the test.
If it's working again, it's probably something wrong on Google's part. I'll try adding a card with systemless root
Ugh, what a headache, I ended up deleting everything for no reason.
Anyone else find it to be working now? I ran the safety net check last night and it passed. Tried adding my card and this time it worked. Big G must have fixed something on their end.
Good morning! Alright. So. All I've done to my phone was Root it and get Xposed on it. Everything was completely fine until last night. Now, whenever I try to download anything from the Playstore, it just gets stuck on "Downloading". I've tried wiping its cache, its data, force closing it, reinstalling the update. Nothing seems to solve this issue. I was wondering if anyone else has run into this issue on this phone, and how they resolved it? I can't even update my applications, and I didn't even get a chance to Update my Phone, but now when I try to Scan for Updates, it just gets stuck searching :/
This happened to me at first. What worked for me for a couple days was to toggle airplane mode. Then, it started getting stuck again. So, I downloaded Beans GAPPS, and extracted Google Play services and Play Store.apk, and that seems to be working. Keep in mind, that not everything is going to work smoothly. If none of this works, look for the .apk and move it to your device and install it that way. Hope that helps, bud.
I tried Googling Beans GApps, but it seems like they haven't been updated in about a year. Or am I looking in the wrong places?
This has also been my problem since getting a pixel 2 xl almost a month ago. In fact, I wanted to make a thread about my issue earlier but I'm just too lazy! The only thing I did at first was to unlock the bootloader.
Now, I am completely stock without even root but my playstore downloads are stuck in "downloading" and usually the download starts after being stuck in this phase with about 15-30 minutes delay (which could even be hours before my download is finally started, so it's random). The funny thing is playstore lists my device certification status as "uncertified" in the settings. I have tried clearing cache+data of play services+play store+removing/adding my Google account. I also did a fresh and clean install of the May security update rom but all to no avail. I remember reading in another thread that Google may impose a 7 day lock or something for your Google account in these instances so at this point I am just waiting it out (only 3-4 more days remaining) to see if my problem goes away by itself, otherwise, I am pretty clueless as to what I should do next.