Just sharing this, just incase anyone wasn't aware.
My son got Andriod Pay working on his P9000 - credit goes to the Universal SafetyNet Fix by Deic here:
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Simply instructions if already rooted with Magisk here:
http://bbs.elephone.hk/forum.php?mod=viewthread&tid=13626#lastpost
Andriod Pay works fine for him with no issues at all on my old P9000 (which I gave him) :good:
It works. Well done and thanks for posting.
jbs4 said:
It works. Well done and thanks for posting.
Click to expand...
Click to collapse
No probs, glad it helped
It does not work for me.
Maybe because I had superSU installed.
I unistalled superSU and reinstalled magisk v12 with magiskSU but still does not work (neither stable nor beta version of the module).
Any suggestion other than reinstalling the ROM again?
Thanks.
Edit
malomehi said:
It does not work for me.
Maybe because I had superSU installed.
I unistalled superSU and reinstalled magisk v12 with magiskSU but still does not work (neither stable nor beta version of the module).
Any suggestion other than reinstalling the ROM again?
Thanks.
Click to expand...
Click to collapse
As far as I know my son did do a fresh install of Nougat 7, (as he had issues initially with this fix) then installed TWRP recovery and rooted with Magisk 12 (just using Magisk - no SuperSU installed), just make sure in Magisk Manager app that Busybox, Magisk Hide and Systemless Hosts. are enabled in the settings. Not sure if that helps, but my sons is rock solid, SafetyNet Passed Green all the tie and app runs with no issues.
Btw remember to not have any other modules active in Magisk (obviously apart fromUniversal SafetyNet Fix v1.10.1) while setting up, even after successful setup "some" modules may affect this fix, check the thread at https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431 for more about that
It does work, great job just unfortunately for me it doesn't work in my Country. Thanks any way
I finally made it work.
My problem was the Magisk Manager version I was using, 5.0.2.
I downgraded to Magisk Manager 4.3.3 where the settings are totally different and applied the settings from the screen shots of the first post and that did the magic.
Thanks for all the information provided.
Has anyone successfully completed an android pay transaction? I have successfully registered 2 cards but I am not getting any action at Costa's terminal in UK.
fillippe said:
Has anyone successfully completed an android pay transaction? I have successfully registered 2 cards but I am not getting any action at Costa's terminal in UK.
Click to expand...
Click to collapse
I tried at an M&S shop but nothing happened, or so I thought. However, awhile later I got a message from the Android Pay app asking did I have a problem as it knew an attempt had been made. One of the suggestions was that I needed the screen on at the time for it to work, which I didn't do. I thought I had read that the screen didn't need to be on but obviously it does. I haven't a a chance to try it again yet.
Does this still work if I update Magisk to 13.1?
techtalkonline said:
I tried at an M&S shop but nothing happened, or so I thought. However, awhile later I got a message from the Android Pay app asking did I have a problem as it knew an attempt had been made. One of the suggestions was that I needed the screen on at the time for it to work, which I didn't do. I thought I had read that the screen didn't need to be on but obviously it does. I haven't a a chance to try it again yet.
Does this still work if I update Magisk to 13.1?
Click to expand...
Click to collapse
I've updated to 13.1 and it's still passing safetynet.
Does anyone know where the NFC contact area is on the phone?
I've tried 4 times, twice with visa debit and twice with amex. Last 2 times I got the green tick but the payment machine did not react. Very last time I got a message saying something to the effect "we can tell your device is not untouched!", so they could not go forward with the payment, because it couldn't be secure.
So, for me, android pay is still not working.
Haven't tried a payment on the phone yet, however, i did have to modify the build.prop to fully emulate a Nexus 6 and allow me to download android pay from the play store.
Original build prop:
ro.build.flavor=full_c239v55_dx-user
ro.product.model=P9000
ro.GYRO_CALIBRATION=AGOLD_GYRO_CALIBRATION_SUPPORT
ro.product.brand=Elephone
ro.product.name=Elephone
ro.build.tags=release-keys
ro.product.device=Elephone
ro.product.board=Elephone
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=Elephone
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=mt6755
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Elephone
# Do not try to parse description, fingerprint, or thumbprint
CURRENT BUILD.PROP
ro.build.flavor=full_c239v55_dx-user
ro.GYRO_CALIBRATION=AGOLD_GYRO_CALIBRATION_SUPPORT
ro.product.model=Nexus 6
ro.product.brand=google
ro.product.name=shamu
ro.product.device=shamu
ro.product.board=shamu
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=Motorola
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=mt6755
# ro.build.product is obsolete; use ro.product.device
ro.build.product=google
# Do not try to parse description, fingerprint, or thumbprint
You will notice, some of the lines have been changed, *ro.build.tags=release-keys* - deleted from between ro.product.name and ro.product.device, as there are two of these in the file. I also moved the ro.product.model to below the GYRO line, I don't know if that will make any difference.
These changes were made, after I found that android pay was "compatible" with my Zopo speed7+ in playstore, that phone doesn't even have NFC.
These lines also open up google dialer v10 and other google only apps which may or may not work. I also have the latest pixel experience working too. this may even sort out the spam caller issue.
N.B. You will still need Magisk running to pass the safetynet.
Update:
For those of you who are reporting that android pay does not register with the card reader on your P9000, it is most likely due to the type of NFC chip that the phone has. The main standard that supports contactless payment, is Mifare which, is an NXP brand name. Obviously Elephone weren't going to shell out on an NFC chip that is going to cost them megabucks, not when they can fit one that costs pennies. By the time anyone has realised that android pay will never work, the phone will no longer be supported, hey presto, you've sold every unit you needed to make to be in profit, and hoodwinked everyone into thinking that the phone is android pay compatible.
Anyone noticed that Elephone have made no more phones since, with NFC, they have returned to hotknot, which doesn't do much at all.
As I am usually browsing the S8 threads these days in XDA, I just noticed the comments on this thread & thought I would update on this. I spoke to my son and asked him if he was finding using the Andriod Pay app ok on the phone (he works over in Germany so I dont speak that often to him) He has said that he only managed to use the app on one occasion in Sainsbury's while here in the UK, however hasn't used again as he was constantly getting issues at paypoints and couldn't work out why ?? He would then receive an email from Andriod Pay saying something like "We see you had issues using andriod pay" etc & to "ensure the handset is actually on when using the app" He tried all that but to no avail & kinda gave up. He thought maybe it was just his card that he had registered.
So maybe the NFC chip (as stated above & doesn't surprise me one bit when it comes to Elephone) is a cheapy and simply not fit for purpose. My sons now using his mates Sammy S7 now, so no longer uses the P9000.
Unfortunately, it seems as much as you can install the Andriod App . add cards and bypass the security with SafetyNet Fix etc.. when it comes to actually working fully at the paypoint seems to be a mystery / hit n miss, it may work sometimes and other times it wont ;-( I guess the fact Google themselves stated the handset isn't compatible with Andriod Pay (as read HERE) is an indication that maybe its just not possible to use it with the P9000 after all
Ah well ;-( .. I thought I would initially share this as I though "finally" you would be able to use Andriod Pay, but seems this just isn't the case, well without issues that is
jotei66 said:
As I am usually browsing the S8 threads these days in XDA, I just noticed the comments on this thread & thought I would update on this. I spoke to my son and asked him if he was finding using the Andriod Pay app ok on the phone (he works over in Germany so I dont speak that often to him) He has said that he only managed to use the app on one occasion in Sainsbury's while here in the UK, however hasn't used again as he was constantly getting issues at paypoints and couldn't work out why ?? He would then receive an email from Andriod Pay saying something like "We see you had issues using andriod pay" etc & to "ensure the handset is actually on when using the app" He tried all that but to no avail & kinda gave up. He thought maybe it was just his card that he had registered.
So maybe the NFC chip (as stated above & doesn't surprise me one bit when it comes to Elephone) is a cheapy and simply not fit for purpose. My sons now using his mates Sammy S7 now, so no longer uses the P9000.
Unfortunately, it seems as much as you can install the Andriod App . add cards and bypass the security with SafetyNet Fix etc.. when it comes to actually working fully at the paypoint seems to be a mystery / hit n miss, it may work sometimes and other times it wont ;-( I guess the fact Google themselves stated the handset isn't compatible with Andriod Pay (as read HERE) is an indication that maybe its just not possible to use it with the P9000 after all
Ah well ;-( .. I thought I would initially share this as I though "finally" you would be able to use Andriod Pay, but seems this just isn't the case, well without issues that is
Click to expand...
Click to collapse
Strange thing is, I tried mine in a Sainsbury's tonight, and it worked there. I will try this in a few other places and report back, it obviously does depend to the NFC chip installed in the reader, I also have a company Blackberry DTEK50, which does support Mifare NXP, that never seems to have any issues with Android pay.
However, after the mods I've made to the build.prop file, i may not get so many issues, as I was able to install android pay through Play store, when I tried to install it through an unofficial source, my bank wouldn't authourise the card.
so, we're now able to install Android Pay with these tricks, but we're not able to make payments with it? hahaha, that's so elephone
farsiray said:
so, we're now able to install Android Pay with these tricks, but we're not able to make payments with it? hahaha, that's so elephone
Click to expand...
Click to collapse
It ain't working for me...
This guide no longer seems to work.
Whenever I try to install the safety fix it says "installation failed", no error messages.
I've been using Android Pay for a while now on my P9000 - I'm on Deepflex's LineageOS ROM (14.1) with Magisk and the Universal Safetynet Fix. When I first added my card it was blocked by the bank, but after a brief phone call they authorised it and I've been using it at my local Co-op supermarket without issue.
Related
I am running Netflix version 3.9.1 build 4105 and Android 4.4.2.
When I open Netflix the program just sits and spins and spins then gives me a "Sorry we could not reach Netflix Service. Please try again later (-9)". Then I clear app data and after I do that and relaunch then I get the extremely common 15001 error (that is impossible to actually troubleshoot..).
I have read multiple people having issues with Netflix, but that was when they released a patch that broke it and I am pretty sure that isn't a common problem anymore. I have one of the apps that show network activity and all I get is random hits of like 20-30 KB/s max while trying to launch Netflix. I have tried this on two completely different networks, so I don't think it has anything to do with my network.
My device is rooted with TWRP installed, but I don't see how this could have any affect on Netflix (it never did on my old rooted Nexus 7 running Cyanogen Mod).
Is there something I can try that maybe I haven't heard yet? I even tried clearing the Google Services Framework cache/data (as this helped people in the past) and that changed nothing above. Not being able to use Netflix is a huge problem for me and I am hoping someone has run into this on our devices. I imagine Netflix is one of the most common Apps used.
Thanks for any help or ideas anyone can provide. If I need to I'll restore the tablet with Fastboot, but there is no guarantee that will work and an obvious pain if it doesn't.
Edit: Read the latest comments on Netflix and it seems there are still plenty of people having problems just like mine. I guess I may be waiting for a new version to release??
NCSUZoSo said:
I am running Netflix version 3.9.1 build 4105 and Android 4.4.2.
When I open Netflix the program just sits and spins and spins then gives me a "Sorry we could not reach Netflix Service. Please try again later (-9)". Then I clear app data and after I do that and relaunch then I get the extremely common 15001 error (that is impossible to actually troubleshoot..).
I have read multiple people having issues with Netflix, but that was when they released a patch that broke it and I am pretty sure that isn't a common problem anymore. I have one of the apps that show network activity and all I get is random hits of like 20-30 KB/s max while trying to launch Netflix. I have tried this on two completely different networks, so I don't think it has anything to do with my network.
My device is rooted with TWRP installed, but I don't see how this could have any affect on Netflix (it never did on my old rooted Nexus 7 running Cyanogen Mod).
Is there something I can try that maybe I haven't heard yet? I even tried clearing the Google Services Framework cache/data (as this helped people in the past) and that changed nothing above. Not being able to use Netflix is a huge problem for me and I am hoping someone has run into this on our devices. I imagine Netflix is one of the most common Apps used.
Thanks for any help or ideas anyone can provide. If I need to I'll restore the tablet with Fastboot, but there is no guarantee that will work and an obvious pain if it doesn't.
Edit: Read the latest comments on Netflix and it seems there are still plenty of people having problems just like mine. I guess I may be waiting for a new version to release??
Click to expand...
Click to collapse
I have the exact same problem! No matter what it's the same error, restoring the tablet doesn't work either.
Screw Netflix, use TV portal! https://drive.google.com/file/d/0BzI_9bXSPgLUX0kwVV8wd3lsTGM/view
When you grab a movie with TV portal, then use Tubemate to download mp4 quality movies of your choice. (touch the green arrow above to get the download interface)
http://www.androidfreeware.net/download-youtube-tubemate.html
I don't think anyone has problems these days ripping off movies, however streaming thousands of movies and TV shows is more convenient by a mile (especially on a tablet).
That is indeed one reason Google & apple push to get rid of the power of personal storage and force the cloud.
When Netflix won't work when you finally settle for a movie, it's nice to have options.
The measly amount Netflix charges is worth it, they have a good service....
But as you know, traveling you are forced to use sporadic data on the road that cost. Until they fix that, I want my storage.
Thank you for starting this thread driving me nuts today! Thought I was alone. It's my son's tablet and Netflix is one of his major uses for it. Tried so many fixes and none are working. Guess we'll keep an eye out for an update.
Also, anyone have trouble with Netflix in general? I had to install an xposed mod just to get it to run!?!
Edit: I tried a much older version of Netflix and it's working perfectly: http://www.apkmirror.com/apk/netflix-inc/netflix/netflix-3-2-0-build-1340-apk/
I then updated the app again and it refused to load at all. Rolled back and turned off auto updates.
How do you turn off auto updates for a single program? I know how to turn it off completely, but is there a way to do it just for Netflix? It's not like we can deny it network connection..
Also does anyone know the last Netflix version that did work? I think it was around December 2014.
I can also confirm that Netflix 3.2.0 build 1340 does work.
NCSUZoSo said:
How do you turn off auto updates for a single program? I know how to turn it off completely, but is there a way to do it just for Netflix? It's not like we can deny it network connection..
Also does anyone know the last Netflix version that did work? I think it was around December 2014.
I can also confirm that Netflix 3.2.0 build 1340 does work.
Click to expand...
Click to collapse
Go to Netflix in the play store then hit the three buttons in the top right and the option to disable auto updates should be there.
Never got around to testing other builds as that on works fine for my kid.
I believe the reason behind new versions beyond 3.7.1 not working is because of below;
"As of version 3.7.2, Netflix has begun using Forced Google DNS lookup for their Android app. This means that the Netflix app bypasses any DNS servers you setup on the Android device or on the router and uses Google DNS instead.
Traditionally we were able to block Google DNS lookups on the router and force Netflix to use alternative DNS. However, the Android app seems to not work at all if Google DNS is blocked."
In any case I can confirm that version 3.7.1 build 1711 does work as it should.
Also as recommended earlier you have to stop the app prom auto updating.
Hope that helps.
Got the 6p and saw in the settings tap and pay and got excited . However I tried to find Android pay and couldn't so then checked on the playstore and it not there for me (UK). Found a link to it off a YouTube video and it says that it is not available for my country
Anybody know when it will come out or possible way to work around the issue.
Google have released absolutely nothing on it, and I cant find any alternative method either except bPay for barclays users.
I think this is partly because nearly everybody has a contactless card in the UK, it's not going to be a pressing issue for most users, and I don't think too many people use Apple Pay over here either
I tried to use Android Pay this afternoon here in the UK, and in two different shops my Android Pay has stopped working. NFC is on, Android Pay is set to default, open app is disabled. It's not my card/account because I used my card to eventually pay. Anyone else having issues?
This the same as Google Pay? GP works for me alright
Yes same as Google Pay, that's what I meant. Still not working!
It's working here. I updated to the latest version gpay.
Gpay is working correctly here too.
after getting the update from one plus for 6T to android 10.3.0. the play store pops up say "device is not certified" now I cannot use Google Pay. Is there any way to fix this
My phone is a T-Mobile to International Conversion no root or bootloader is lock
From my understanding I'm in the same boat, the only fix I see in other forum's is rooting, or waiting for TMobile to put out a10. Which will probably take along time
This has been answered many times.
To be certified by Google, the ROM digital fingerprint must be communicated to Google by the manufacturer.
As you have modified your device by installing an OOS designed for another phone (yes technically global OP6t is a different phone compared to TMob one), there is a mismatch in parameters transmitted to Google leading to a non certified device.
The only solution is to root and use a Magisk module to modify your phone digital fingerprint towards a recognized one. (Magiskhide props config)
Complaints are to be addressed to TMobile.
Is this still an issue? I'm rooted and use Magisk to certify but I can't play games like Mario Tour and I'm considering going back to stock.
Striatum_bdr said:
This has been answered many times.
To be certified by Google, the ROM digital fingerprint must be communicated to Google by the manufacturer.
As you have modified your device by installing an OOS designed for another phone (yes technically global OP6t is a different phone compared to TMob one), there is a mismatch in parameters transmitted to Google leading to a non certified device.
The only solution is to root and use a Magisk module to modify your phone digital fingerprint towards a recognized one. (Magiskhide props config)
Complaints are to be addressed to TMobile.
Click to expand...
Click to collapse
I just wanted to say thank you for sharing this.
I know these types of things are shared in many places, but unfortunately its hard to figure out where to look sometimes. So thanks for being redundant it was helpful!
Anyone facing this problem? My google pay is inconsistent when on public transport and in retail stores.
Could it be software issue?
Can you type Oxygen version, root or no? And can you find in Google play settings certification of you device?
alf_and_co said:
Can you type Oxygen version, root or no? And can you find in Google play settings certification of you device?
Click to expand...
Click to collapse
Also having problem with my NFC with public transport.
Never work for public transport before, but ok with retail payment
my is Oxygen OS 10.5.10.IN11AA, no root.
not sure if this is the Google Play Cert
Version 20.6.19-all [0] [PR] 316598174
OOS 10.5.10.IN11AA
Google Play Services Version 20.21.17
Google Pay Version 2.111.306
I tried toggling on the '' non standard NFC tag support '' in developers option. Doesnt work as well.
Many op8p users also faced the same problem in my country.
Tried re-adding my cards several times, cleared cache of google pay,google play services,google framework.
Downgrading app versions.
On public transport, my phone just vibrates and will prompt " does not work " or " move closer ". Never worked, receiver receive nothing.
In retail payment, it worked about 90% of the time with 10% requiring to tap twice.
I have similar issue.
- I use polish banking application that uses NFC for contactless payment.
- In retail payment, 90% of the time is successful, 10% requires to tap again.
- In vending machine almost every payment is rejected (I got 1 successful payment but I can't reproduce it again). I used same banking application on my xiaomi mi8 with same vending machine and worked good.
- I tried google pay and it doesn't work too (at least it shows some error on screen)
- no root, oxygenos 10.5.9.IN11BA
In conclusion it's not a problem with google pay but with nfc as other payment apps have same problem.
IIRC on the teardown video, the NFC chip is in behind the camera. It's maybe in too deep inside the phone for it to work correctly everytime.
Sent from my IN2023 using Tapatalk
Came looking to see if I was the only one with an NFC issue
Mine has been working perfectly since I got the phone, then yesterday I went to use it at a POS in a shop and it wouldn't work......move closer/slower etc. so I used my bank card itself.
I got the train and said I had low balance when I got off so went to top up my leap card (Irish transport card) and it fails the second it tried to read the card.
FYI I have sucessfully topped up my leap card dozens of times on the phone.
Next I went to get something to eat. I tried using it at the restaurant POS and worked first time, no problem.
Then this morning I just tried using it in shop POS and everytime it pinged and gave me a tick mark and showed the card as if it completed OK but the shop unit did not register anything (I also know the transaction did not go through as revolut did not show the transaction). I used my bank card and it worked.
I have just tried my leap card again and it is still not working.
This is very frustrating as I use NFC payment everywhere.
Anyone know if I can see logs for the NFC chip?
Why did it suddenly just stop working, I haven't had any updates.
Running Oxygen OS 10.5.12.IN11BA
Play services Version 20.33.14(120400-327249014)
Google Pay Version 2.116.328438545
Not had this problem before, could your case be the cause? Or anything else in your hand?
The range has impressed me with mine.
Currently rooted and using xXx and Gpay is still good.
It looks the oneplus 8 pro nfc chip is very weak. For me the strongest signal is under oneplus logo on the back. I found out the nfc chip is under the keypad at vending machine (not under display). Now to make it work I must keep my phone very closely to the terminal.
I need to get close on a number of NFC readers...no biggie.