Database Develop

Anyone Unlocked?

Has anyone been able to unlock their TF701 with the Asus Unlock Tool? I get the dreaded unknown error message that plaqued previous Transformers: unknown error occurred , which may be a network error please try later.
On previous Transformers I know it had to do with serial number issues. I checked the serial in settings and it matched the serial on my box. I literally just charged my tablet, and then immediately tried to unlock so I know it's not an app issue or anything like that. I don't even have Google synced. I just turned on Wifi and tried to unlock. I noticed that I was running an older firmware so I decided to manually upgrade that (auto upgrade didn't work even after clearing those two apps, can't remember their names) and the same error occurs. Tried rebooting of course and still nothing.
I'm guessing the unlock tool just isn't working right now? Sucks since I'm going to end up restoring all my stuff and then having to format during a future unlocking.

OP here with an update. I contacted Asus Support and they suggested a factory reset. Didn't think it would work but tried it anyways and of course it didn't. Any ideas out there...anyone successful with unlocking their 701?

below_radar_00 said:
OP here with an update. I contacted Asus Support and they suggested a factory reset. Didn't think it would work but tried it anyways and of course it didn't. Any ideas out there...anyone successful with unlocking their 701?
Click to expand...
Click to collapse
if there is root it will be in the development thread. patience:good:

AngryDinosaur said:
if there is root it will be in the development thread. patience:good:
Click to expand...
Click to collapse
this isnt about root. but i have same problem, talking to asus couple days they requested a screen shot of my device ids. sent that today, said they talking to tw headquarters about it.

AngryDinosaur said:
if there is root it will be in the development thread. patience:good:
Click to expand...
Click to collapse
Thanks for the reply but this isn't about root. This is about unlocking the device.

I'm ready to unlock too. Haven't tried yet, as after reading your experiences in guessing Asus needs to update. But if I can do anything to help, please let me know.
Sent from my K00C using Tapatalk 4

i unlocked the ww 45, then manually upgraded to ww 47, because no matter if locked, automatic update didn't work.
what i noticed is, the unlocking made an extra 2 or so reboots and seemed to hang somewhere in between for a couple of minutes.
however it worked.
also nothing prevented me from reinstalling the update again, even already running ww 47.
another thing i noticed is, a wd my passport drive shows up as a memory card, but updating from there is not possible.
in my case it only accepted it from the 'internal' microsd (i used a 64GB sandisk)

lpdunwell said:
i unlocked the ww 45, then manually upgraded to ww 47, because no matter if locked, automatic update didn't work.
what i noticed is, the unlocking made an extra 2 or so reboots and seemed to hang somewhere in between for a couple of minutes.
however it worked.
also nothing prevented me from reinstalling the update again, even already running ww 47.
another thing i noticed is, a wd my passport drive shows up as a memory card, but updating from there is not possible.
in my case it only accepted it from the 'internal' microsd (i used a 64GB sandisk)
Click to expand...
Click to collapse
are you using the us tablet for world wide update?

lortay78 said:
I'm ready to unlock too. Haven't tried yet, as after reading your experiences in guessing Asus needs to update. But if I can do anything to help, please let me know.
Sent from my K00C using Tapatalk 4
Click to expand...
Click to collapse
Once you try it, let us know. I still can't get it to unlock. I have the US version.

below_radar_00 said:
Has anyone been able to unlock their TF701 with the Asus Unlock Tool? I get the dreaded unknown error message that plaqued previous Transformers: unknown error occurred , which may be a network error please try later. I don't even have Google synced. I just turned on Wifi and tried to unlock. I noticed that I was running an older firmware so I decided to manually upgrade
Click to expand...
Click to collapse
I am not 100% sure about this but if you don't have your google info entered then the unlock utility cant flag your device in google play to prevent you from downloading DRM content. So unless it succeeds in that connection it won't unlock.
I suppose if you really wanted DRMed content you could get another google play account and unlock..... then maybe not. Personally I dont care about DRMed stuff, I refuse to use software which automatically assumes I'm going to pirate, and cripples my device in the process.

gregpilot said:
I am not 100% sure about this but if you don't have your google info entered then the unlock utility cant flag your device in google play to prevent you from downloading DRM content. So unless it succeeds in that connection it won't unlock.
I suppose if you really wanted DRMed content you could get another google play account and unlock..... then maybe not. Personally I dont care about DRMed stuff, I refuse to use software which automatically assumes I'm going to pirate, and cripples my device in the process.
Click to expand...
Click to collapse
Hmm...that's a pretty good theory! I did end up syncing my Google account late last night after I did a factory reset and it still doesn't work. I just double checked that my account is indeed active and synced and it is. I tried the unlock tool again just in case and same error message. I don't understand why something straight out the box won't unlock with their own tool.

I'm going to wait, I guess, for a recovery before I flip out about this. I seem to remember having to wait for the tool after I finally got my tf201. After owning that device, I really want to make sure I am confident of the hardware. So far, though, it seems great.

lortay78 said:
I'm going to wait, I guess, for a recovery before I flip out about this. I seem to remember having to wait for the tool after I finally got my tf201. After owning that device, I really want to make sure I am confident of the hardware. So far, though, it seems great.
Click to expand...
Click to collapse
It finally works. Tried just now and worked the first time. Must have been an issue with the Asus servers.

[Q] Google wallet tap to pay not working

Greetings,
I've recently switched over from the Samsung galaxy s3 to the m8. I have my phone rooted, but currently on the stock rom. I have Google wallet installed on my phone, and tried to us the tap and pay function at McDonalds. I was unable to get the NFC function to work. I know the store terminal works because I used my stock nexus 7 (not rooted) a few months ago to get some coffee there.
I had the same issue on my s3, but I was running cyanogenmod on the phone, and I thought that was the problem. Now I'm wondering if it's having root access. Anyone else having problems with tap to pay on their rooted phone?

Maybe the store terminal broke since... A few months cab do that try a different store
Sent from my 831C using XDA Free mobile app

I'm having the same issue. For me, the problem started when I switched from a Sprint-specific ROM to Viper ROM (intl base). After 2 minutes of bashing my phone against the terminal at McDonald's, it did finally work. But it is not working instantly like it used to, and it acts like nothing is happening. I know it's not McDonald's terminal because it happens at another McDonald's and Walgreens where previously it was working fine. Tapping my phone to another NFC phone works so NFC itself is working.
I don't really feel like going back to a different ROM over this, but it is annoying.

Only place I have has issues is one checkout lane at meijer. Felt like pretty stupid last night since I left my wallet at home. Cancelled my order, went to a different Lane and it worked fine. So for me at least it's not an issue with the phone

Just wondering if anyone else has experienced this. I still cannot get tap and pay to work. The light on the NFC reader at walgreens will blink once when I tap it, but there is zero activity on the phone even though google wallet says "tap and pay ready". Doesn't work at McDonalds either. Friend can use his Note 3 just fine with google wallet in those locations so I know it's not the NFC reader.
I have tried RUU back to the latest stock ROM, no dice. I re-locked my bootloader and RUU'd back to the oldest available HK ROM and did all the OTAs, still same exact issue. I have not been restoring from backup either so my phone is basically 100% stock now non-rooted. The only difference is it's S-OFF, but I've been S-OFF since June and my tap and pay was working until early September so I don't think that's it. I can use NFC to share things with other phones so I know my NFC is fine.
I'm completely stumped.

I think the nfc antennas on this phone might be too weak, I have to get my phone JUST right to read nfc tags...
Sent from my HTC One_M8 using XDA Free mobile app

I don't think that's the issue I'm having. I bought the phoen right when it came out, and I used NFC just fine at McDonalds and Walgreens without having to fiddle with it. It just worked. Now it doesn't work at all. I don't know what happened, the last time I was able to get it working was early September. Not sure if there was a wallet update or something that broke it. NFC communication to other phones still works fine though.

A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.

om4 said:
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
Click to expand...
Click to collapse
Yep, Best Buy and CVS are the big ones who have disabled it. However, Walgreens and McDonalds have not. They still accept NFC payments via Google Wallet, and it still works on my friend's Note 3 as of yesterday.

Just wanted to say I've had the same problem. It seems to work when it wants to. NFC itself works fine. I feel like it stopped working after the WiFi calling update... If someone's able to go to the previous update and test it would be awesome.

Figures if it affects Apple its all over the news.
http://www.theverge.com/2014/10/25/7069863/retailers-are-disabling-nfc-readers-to-shut-out-apple-pay

My wallet hasn't worked for me the past few times I've tried (at Walgreens and my work vending machine). I'm guessing it has something to do with my ROM (Viper) or a xposed mod I have running (though I don't have much and nothing related to Wallet directly).

After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.

kwolf said:
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
Click to expand...
Click to collapse
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.

henderjr said:
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
Click to expand...
Click to collapse
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?

kwolf said:
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
Click to expand...
Click to collapse
Wallet doesn't react at all if I have it open or not when "tapping" my phone. I think the phone beeps too but can't remember now. I know my nfc works fine as I use a nfc tag every morning when I get to work to put it on silent.

My m8 does the same thing... I figured it was running Viper as well, but I just flashed the newest firmware and the stock rom... Same story. I hold my phone up to the NFC terminal, and the lights stop blinking on the terminal, but nothing happens on my phone. When I use my S4, the terminal beeps, my phone vibrates and it just works. I just tried deleting all my cards and trying again... No dice. I just went through a chat with HTC, and they're escalating the issue, who knows, maybe it's bad hardware. (I've never had NFC working)

Update: htc called to confirm my information and to say the turnaround time is 7-10 days. They mentioned that it's rarely a software problem if you're not getting an error. I'm not. I'm assuming that once they research some more, they'll just end up replacing my phone. We'll see.
Sent from my 831C using Tapatalk

After upgrading Viper to 4.4.4, removing all cards, removing all old devices from here (https://wallet.google.com/manage/#devices:), uninstalling/installing wallet, and adding cards back in and it now works. I don't know which one of those fixed it as I did them all before trying.

Thanks henderjr! I tried everything you had posted there, but still didn't have any luck. (holy crap, I had a ton of devices listed... One for each ROM installed in the past few years.) Hope your information helps someone else get their device working!

Android Pay anyone get it to work?

Just like the title says anyone get it to work in running Clean ROM I get through the whole "add a card" process and then get the not compatible message

mines work. just updated about 2hrs ago. im just waiting to verify my cards

Where'd you get that from? The only option I see is to download the new "Google Wallet" alongside the current pre-installed one.

well yesterday it asked me to update so i updated and then when i launched google wallet it also asked me if i wanted to use google wallet or use the new android pay. i clicked android pay it downloaded it for me and launched at well and its working fine.

Well hell mined keeps telling me the same thing and I just updated right now too...

Well I stand corrected, checked yesterday was nothing even late night...this morning it updated. No errors, runs perfect but yet to try it to actually pay.
*Edit: Used it at Walgreens this morning. Had to hold it to the unit, scan my fingerprint, then remove and hold again. Worked.

Works for me. It imported my credit and loyalty cards from Wallet. I used it this morning and the only thing is it didn't automatically use my Panera loyalty card. But I'm not sure if that functionality is up and running yet.
Sent from my SM-G928V using Tapatalk

I'm having the same issue as you are and I'm rooted - not Rom'd. Did you find a solution?

Not sure if it's the same for rooted s6's as it was for rooted M8's, but if you disable SuperSU temporarily (SuperSU>Settings>Uncheck enable Superuser), then go in to android pay, it should activate. After that, just go back to SuperSU and recheck the enable superuser box.

wolfgrrl said:
I'm having the same issue as you are and I'm rooted - not Rom'd. Did you find a solution?
Click to expand...
Click to collapse
What he said ^ haha but i noticed that if i enable SU again the service won't work when i try to pay

NFC Payments broken?!

Hi,
Has anyone noticed that starting in late April, NFC based payments no longer work?! I wonder because other NFC usage works (e.g. Android Beam or simply reading various NFC tags or cards). I can't figure the exact date, but the last payment that I made with my phone was around 24 april, then it comes the april security update. And after 1 May I noticed that it simply don't work.
Regards

net4u said:
Hi,
Has anyone noticed that starting in late April, NFC based payments no longer work?! I wonder because other NFC usage works (e.g. Android Beam or simply reading various NFC tags or cards). I can't figure the exact date, but the last payment that I made with my phone was around 24 april, then it comes the april security update. And after 1 May I noticed that it simply don't work.
Regards
Click to expand...
Click to collapse
I also have the april security patch, but i could still do a payment yesterday with the NFC of the phone.
So no problem for me.

Yes, Google Pay stopped working for me in mid-April, *but* before I installed the April security patch so that wasn't the cause for me. I was hoping the April patch might fix it but no joy. I've been checking here to see if anyone else had the same problem but this is the first report I've seen.
It's very annoying as I'd got very used to using it... as you say other NFC things are fine.
I've done all the usual tricks of uninstalling, wiping caches, trying an earlier version (it seemed to stop working after the Google Pay update was installed that was released on the 15th, so I thought that might help), etc. etc. but no joy at all. It just doesn't trigger.

Same problem, suddenly NFC doesn't work anymore. Weird thing I discovered is that it might work at that moment when I press the power button to switch display off. ... Strange

Using Magisk with it? Rooted device?

Ah, ok, maybe i wasn't clear enough.
For me it still works, but i do NOT use Google Pay, i use the app from our bank for NFC payments.
I think that i have read some time ago about problems with Google Pay, so maybe that is the case.
I also found out some time ago, that i have to have the lockscreen on-screen, otherwise i cannot do a payment.
So unlocking the phone makes payments impossible and screen-off is also a no-go.
But i suppose you guys already knew that.

xsycox said:
Using Magisk with it? Rooted device?
Click to expand...
Click to collapse
Nope, pure stock (apart from most evenwell apps disabled for this user).
EDIT: Two threads about it now on the Nokia forum at https://community.phones.nokia.com/categories/nokia-7-plus

Fixed by uninstalling Google Pay
Just an FYI, I had my NFC issue resolved by uninstalling Google Pay. May help someone else.

I did not use Google Pay (since is not available in my country), but two tap and pay apps from two banks where I have accounts. Both have updates in april, and one of them tryied to became forced my default one without asking explicitly. But as I say: other NFC functions works: I can beam, I can read tags or cards.

I didn't use Google Pay as well, however, it seemed to interfere with my banking app (couldn't pay anymore) and access to buildings.

Nexustb said:
I didn't use Google Pay as well, however, it seemed to interfere with my banking app (couldn't pay anymore) and access to buildings.
Click to expand...
Click to collapse
No, I mean since is not available in my country yet, I haven't it on my phone.

....and fixed in the latest version of Google Pay, released last week

It may be related to this: https://nvd.nist.gov/vuln/detail/CVE-2019-2041 ?

gPay not workin

I've added PayPal and my Creditcard, both are not working but worked fine on my Pixel 2 XL.
It says: "phone moved too fast" but even if I lay it down on the terminal and not even touched it, the error appears.
Someone can relate? Any advice?

Nope, mine is super sensitive

I have a similar experience. Transferred my three cards from Pixel 4 XL and all of them refuse to authorise a payment on the Pixel 5, despite setting up with no issue. Three issuers (Amex/Nationwide/John Lewis Partnership) and I've tried at least 6 vendors. Just get the "That didn't work" message. Something odd is going on.

darkinformer said:
I have a similar experience. Transferred my three cards from Pixel 4 XL and all of them refuse to authorise a payment on the Pixel 5, despite setting up with no issue. Three issuers (Amex/Nationwide/John Lewis Partnership) and I've tried at least 6 vendors. Just get the "That didn't work" message. Something odd is going on.
Click to expand...
Click to collapse
Update: Have undertaken a full factory reset today and rebuilt the phone without copying across anything from my previous device via cable. Can confirm Google Pay is now functioning correctly.

mine is not working but I dont want to factory reset the device

Same - worked fine on my 2XL, none of my cards (from 2 different banks) working on the 5, just comes up with the "that didn't work - try another card" error, so obviously NFC is fine. Have removed the cards and re-added but no luck so far. Next up is to roll back on Play Services (currently on beta) and see if that works. Don't particularly fancy a reset!

I also had the descibed issues when trying to pay in a store today. Had to resort to my VISA card instead. Got a "transaction failed" error, and the terminal prompted me to insert the card instead. Funny.. hopefully this is just a software issue that can be fixed.
At first I thought it was caused by my root, but I do pass SafetyNet just fine (on basic attestation).

MattSkeet said:
mine is not working but I dont want to factory reset the device
Click to expand...
Click to collapse
Maxr1998 said:
I also had the descibed issues when trying to pay in a store today. Had to resort to my VISA card instead. Got a "transaction failed" error, and the terminal prompted me to insert the card instead. Funny.. hopefully this is just a software issue that can be fixed.
At first I thought it was caused by my root, but I do pass SafetyNet just fine (on basic attestation).
Click to expand...
Click to collapse
Mine now seems to work after rolling back to the non-beta Google Play Services - I did this through the Play Store.
I wouldn't be too surprised if it might have just been clearing Play Services cache/data (which I assume also happened when I rolled back) so maybe try that first!

Did you unsubscribed from beta or just installed?

alastor2004 said:
Mine now seems to work after rolling back to the non-beta Google Play Services - I did this through the Play Store.
I wouldn't be too surprised if it might have just been clearing Play Services cache/data (which I assume also happened when I rolled back) so maybe try that first!
Click to expand...
Click to collapse
Yeah, doing the clear cache and data is probably the first thing I'd try. That has fixed several issues for me over the years on several different apps.

Hi all, hi @alastor2004,
Would you mind to share which "stable" version of Google Pay Services you are on NOW after downgrade?
alastor2004 said:
Mine now seems to work after rolling back to the non-beta Google Play Services - I did this through the Play Store.
I wouldn't be too surprised if it might have just been clearing Play Services cache/data (which I assume also happened when I rolled back) so maybe try that first!
Click to expand...
Click to collapse
My setup of the device was from scratch so I don't think it's a matter of restauration of some backup but I was in the Play Services beta program. I opted out but didn't get any notification about application downgrading back to stable release. My current version of Play Services is v. 20.39.15 (150400-335085612).
Thanks.
L.

GP not working on the P5 is a known issue. Sometimes factory reset works and sometimes not. An update will be coming soon according to Google.

bobby janow said:
An update will be coming soon according to Google.
Click to expand...
Click to collapse
Do you have a source for this information?

ademmer said:
Do you have a source for this information?
Click to expand...
Click to collapse
Here's one: https://www.androidpolice.com/2020/...ecting-phones-from-google-oneplus-and-others/
And another: https://9to5google.com/2020/10/26/some-pixel-5-owners-cant-make-nfc-payments-with-google-pay/

bobby janow said:
Here's one: https://www.androidpolice.com/2020/...ecting-phones-from-google-oneplus-and-others/
And another: https://9to5google.com/2020/10/26/some-pixel-5-owners-cant-make-nfc-payments-with-google-pay/
Click to expand...
Click to collapse
Sure, but I didn't mean a source for the issue (which I am facing myself) but a source that Google is working on a near fix.

ademmer said:
Sure, but I didn't mean a source for the issue (which I am facing myself) but a source that Google is working on a near fix.
Click to expand...
Click to collapse
Bottom of the 9-5 link
Lots of stuff on Reddit too.

bobby janow said:
Bottom of the 9-5 link
Lots of stuff on Reddit too.
Click to expand...
Click to collapse
I do not quite get it. I asked for a proof that Google is already working on the issue. The 9-5 link you provided sais on bottom: "We have reached out to Google for a comment on the issues that some are facing, and will update should we receive an official response."
Means: No official response from Google yet and no confirmation that anyone is already working on a fix. Or am I mistaken?

ademmer said:
I do not quite get it. I asked for a proof that Google is already working on the issue. The 9-5 link you provided sais on bottom: "We have reached out to Google for a comment on the issues that some are facing, and will update should we receive an official response."
Means: No official response from Google yet and no confirmation that anyone is already working on a fix. Or am I mistaken?
Click to expand...
Click to collapse
I was just trying to help you get started. Figure it out yourself.

I had the issue but i removed my card and re-added. its been ok so far

bobby janow said:
I was just trying to help you get started. Figure it out yourself.
Click to expand...
Click to collapse
Wholly jabber Jaws Batman, The peep was only asking for the correct info.
Sent from my Pixel 3a XL using Tapatalk