Database Users

google wallet with root

If device is rooted would I still be able to do wallet without problems?

http://forum.xda-developers.com/showthread.php?t=1779644

[Q] Pac on Samsung Galaxy S1 captivate problems

ME: I am a phone idiot, my first cellphone at all was last fall and I don't know anything, so apologies in advance if I say dumb things because everything is new to me including smartphones themself.
THE PHONE: AT&T unlocked Samsung Galaxy S1 i897 Captivate, not currently activated/no SIM if that matters. Trying to insure it works rooted on kit kat without bricking BEFORE getting the phone back into service.
THE ROM: pac_captivatemtd-nightly-20150124
FWIW i tried kingo-root and it didnt work despite supposing to, used something called Odin v1.85 instead. Flashed I897UCKF1-AutoRoot-DesignGears.tar for Odin, and something called CornKernel UCKK4v705.tar for custom recovery.. Then the Pac-man ROM. I'll note with interest it refused to see the SD card on reboots, had to use internal storage. Didn't quite understand what to do with the gapps [which it wont let me link here i see] fwiw other than copying it onto the phone somewhere. All reboots seem to get back to a working install - but then I can't do anymore more with it.
It accepts wifi login stuff for local connection but I cant get it to log into the Google Play store stuff. I get "unable to connect to google servers", the button to connect to the google account doesn't work/you can hit it a hundred times and it does nothing until you skip past it, and comments about google services framework crashing, google play services crashing, google account manager crashing...
How do I start narrowing down where the problem is, is this about Pac Man rom or the GAPPS or something for a samsung captivate-specific subforum?

Sold Nexus 6p

I sold a nexus 6p online. I shipped it out to the buyer. He received it and he is unable to sign into his account on the phone. It is telling him that it's still attached to my account. I was wondering if there was a way to remotely delete my account so the buyer and sign into it with his account.

mflammger said:
I sold a nexus 6p online. I shipped it out to the buyer. He received it and he is unable to sign into his account on the phone. It is telling him that it's still attached to my account. I was wondering if there was a way to remotely delete my account so the buyer and sign into it with his account.
Click to expand...
Click to collapse
Search google for FRP (factory reset protection).
As far as I know there is no way to do it remotely. I think you should have signed out of your google account before you reset the phone. Most likely he will have to ship it back to you so you can sign in and then remove your account.

Here: https://security.google.com/settings/security/activity?pli=1
But I'm not sure how that will affect the device.
You could always change your password to something stupid for a few seconds for him to sign in and sign out depends how sensitive data you have on your account..

Will Android device manager do it? Will it remotely wipe the phone and remove my account from it, or will it flag the phone as stolen. I cannot get any solid information from repeated Google searches as to what happens after the device is remote wiped.

Android Manager will wipe the device but when it turns on it will ask for any Google account it was bound to before wipe. The other person needs to enter your Gmail account, then his, then you can either change password to your account or wipe it with Device Manager and next time it boots it will accept your account or his (because both were added before wipe).

You can always set a temporary password to your Google account, send it to the buyer and have him log in with his account. After that, you change your password back and voilà.

Is all of this a working protection against simply Fastboot unlocking bootloader, flashing stock image then rebooting into a working phone?

Mangala_Dharma said:
Is all of this a working protection against simply Fastboot unlocking bootloader, flashing stock image then rebooting into a working phone?
Click to expand...
Click to collapse
If the bootloader is currently locked, I believe you would have to go into developer options to enable the OEM unlocking setting... Which you can't get to because of the FRP.

Mangala_Dharma said:
Is all of this a working protection against simply Fastboot unlocking bootloader, flashing stock image then rebooting into a working phone?
Click to expand...
Click to collapse
Unlocking bootloader (OEM unlocking in dev options) deactivates this protection but to do it you still need to get in there somehow and you can't without first logging into a Google account it is currently bound to. And as you probably know without unlocked bootloader you can't flash anything.
And even if he could flash new ROM my friend had bought used Samsung S7 Edge and previous owner also left it locked. You can flash different ROMs with S7 Edge out of the box but the FRP survived several attempts at flashing stock/custom ROMs. We had to use the workaround found here at xda S7 forums.

Thanks for all the info.
I did not unlock the bootloader on the phone. I read a little bit about Factory Reset Protection and the only way around it was to sign in to the phone and then remove your account from the phone. It's something that was new this year for Android devices and I was just unaware of it.

It's actually been around awhile, just not widely implemented. If you remember which monthly security update you last installed, he might be able to get around it. YouTuber root ninja has some videos depending on patch. The one I watched just for kicks (since I'd like my 6P to be protected if lost) was a few months old though.
Sent from my Nexus 6P using Tapatalk

I heard that with a simple factory reset with the stock recovery should remove the account from the phone.

Lol good luck with getting that off remotely it's impossible it's kinda like apple cloud system which is really good.

Android/Google pay, cant pay in shops.

Hello,
Before rooting and custom rom, I wasnt able to pay with the phone. After custom rom and root, Im still not able to pay. When rooted, I wasnt able to add the paying card to the app, so I fully unrooted the phone. Then I was able to add a card, but still I cant pay with the phone. I have tried 3 batteries, with NFC.
Is there a fix or some kind of update for it ?

Google Pay/Wallet

I'm a user who really loves these apps - however they are not available in my region and when I download download them I am told "Google Pay is updating at the moment, so you won't be able to access the app." Is there any way at all to fix this? I can install any apps needed, as long as they don't need root.

You can use a foreign VPN or change the CSC on your phone to launch the app without this message, but the payment itself will still remain an issue.

Sorry I'm new to this. What would changing my CSC do? I have the UK BTU one. And how would I do it?

Also which apps are the one which the VPN needs to change? I'm using Orbot.

Note that if you're rooted Google Wallet may detect it and stop you from using it: https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703

aricooperdavis said:
Note that if you're rooted Google Wallet may detect it and stop you from using it: https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703
Click to expand...
Click to collapse
Not rooted, it used to work until I updated it.

I have a non-rooted Galaxy S20+, Germany (DBT) CSC and it's stuck in Google Pay is updating.
Tried clearing data/cache and uninstalling/reinstalling Google Play Services and Google Pay.
Have had this issue for months and I ignored it, but now that Google Wallet is a thing I wanted to try it but no luck.

Any ideas?

try this:
1) unlock bootloader
2) fastboot erase cust
3) relock bootloader
see if it works that way after setup.
P.S.
You must enter a pin code during setup for google pay to show up.

Hi guys,
I am posting here in hopes that my solution will help you also!
I have a stock Mate 20 Pro and a few days ago after a factory reset I,ve encountered the "Google Pay is updating at the moment, so you won't be able to access the app." error.
I am from Romania and here GPay transformed onto GWallet. But never the less the error is the same. I've tried all solutions found on the Internet but none worked( clear cache for G play services and G play store, uninstal and reinstall GWallet app, install older versions of GPay and GWallet, even formatted the phone once more). Nothing worked.
The solution that worked for me and there is no reference of it over the net:
1. Find/install on the phone the proprrietary wallet app. Eg: For Huawei - Huawei Wallet, for Samsung - Samsung wallet/Samsung Pay.
2. Open it and give permissions to everything that is asking for. Go until adding a card if it lets you but do not add it.
3. Close the app.
4. Open Google Wallet / Google Pay depending on the country you're in.
5. Enjoy once again GPay!
Hope this will help!