Related
This is the place to discuss anything and everything related to SuperSU and SafetyNet / Android Pay.
To clarify, I am not currently actively doing any development on having SuperSU pass SafetyNet detection, or having Android Pay work; the same way I put no effort into beating other root detection methods such as various enterprise security tools.
In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU.
While I may not agree with Google's stance, I'm not about to go messing with payment systems. Is it possible though? Probably yes.
This thread has been created because you guys simply cannot stop talking about this, so these posts can now go here, where I don't ever have to see them.
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
0.0 said:
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
Click to expand...
Click to collapse
Root is a no no with android pay and I think custom ROMs are also out at the moment
Sent from my A0001 using Tapatalk
Pure Drive GT said:
Hey, thanks for your continued support for root on Android, was just wondering, is google making it harder to achieve decent root privileges, as in they don't want rooted devices or are they just unrelatedly changing up things which forces you guys to adapt?
On another note, is there any progress on root without the modded boot? This is by no means an ETA, just wanted to know if you think it's possible or the situation looks rather dire.
Thanks again for your many efforts!
Click to expand...
Click to collapse
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Many banking and financial apps restrict access on rooted devices; it's not just Google.
It makes sense in some ways: root access allows running things in the background to either circumvent, monitor, or interrupt program transactions. They're being paranoid, and I don't blame them.
I don't like the Google Pay concept (or Apple's either); like every other encryption or security system, it's destined to eventually be hacked.
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Yep, I was able to add my debit card but not credit.
VZW LG G4
mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...hy-android-pay-doesnt-support-rooted-devices/
shaggyskunk said:
Yet the Note 5 has been rooted for at least a couple of weeks
Click to expand...
Click to collapse
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Srandista said:
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Click to expand...
Click to collapse
I believe that it's only at&t and Verizon that locks the bootloader - And none in Canada and many other Countries.
Sent From my SM-N910W8 Running SlimRemix V5.1
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
NYZack said:
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
Click to expand...
Click to collapse
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Lrs121 said:
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Click to expand...
Click to collapse
I also found that having an unlocked bootloader will stop Pay working. When MM released I decided to go fully back to stock but kept the bootloader unlocked so I could flash MM. Pay still failed, so I've given up and gone rooted again.
Sent from my Nexus 6 using Tapatalk
Ch3vr0n said:
@Chainfire if you actually are able to pull off fully working stable root WITHOUT modifying the /system does that mean you MIGHT have opened the door into having root AND still being able to get OTA's?
Click to expand...
Click to collapse
osm0sis said:
Yup, all you'd need to do is reflash stock kernel to pass the boot partition EMMC check, or, we could automate restoring the previous stock kernel, flashing the OTA and then injecting the new stock kernel with root after flashing (à la AnyKernel2 or MultiROM). So many exciting possibilities there where custom recoveries are concerned.
Click to expand...
Click to collapse
Chainfire said:
Honestly it's not so different from using FlashFire to flash re-flash system, then OTA, then re-root. But it is easier, yes.
Click to expand...
Click to collapse
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Andrew Morykin 12:24
This should retain Android Pay, right?
Click to expand...
Click to collapse
Chainfire 12:58
+Andrew Morykin if it does, then it's by accident and not by design, and Android Pay will be updated to block it.
Click to expand...
Click to collapse
https://plus.google.com/+Chainfire/posts/aJbqUZ8PEP4
also, I was confused by this:
Chainfire said:
- I have not tested with encrypted devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935
Aren't
Nexus 6P / angler
angler-mdb08k-boot-systemless.zip
Click to expand...
Click to collapse
and
Nexus 5X / bullhead
bullhead-mdb08i-boot-systemless.zip
Click to expand...
Click to collapse
encrypted out of the box?
dabotsonline said:
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Click to expand...
Click to collapse
How is that a downside?
It's exactly the same with every other form of root you will ever see. They don't want to support Android Pay (and some other stuff) on rooted devices. If we find a root that allows it, they will update their system to detect and block it. That cat and mouse game will not end as long as Google doesn't want Android Pay on rooted devices.
Maybe someone will make apps/modules that help circumvent this, but it certainly will not be me.
also, I was confused by this:
Aren't
Nexus 6P / angler
and
Nexus 5X / bullhead
encrypted out of the box?
Click to expand...
Click to collapse
Still can't test what I don't have.
russlowe73 said:
Factory images
Click to expand...
Click to collapse
So basically I have to go back to 100% stock using ADB, and then flash the new SuperSU stuff with any custom ROM? If so, what are the benefits of this other than getting Android Pay while rooted?
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of root on the Nexus 6!!
efrant said:
Starting with Android 5.0, OTA updates are now block-based rather than file-based, so any modification to the system partition will cause the OTA to fail, even mounting the system partition as r/w.
Click to expand...
Click to collapse
Just to add to this, it's a whole-partition /system patch OTA if the device launched with Lollipop or later, anything that launched with KitKat is still receiving the old file-based patch OTAs. Modifying Settings.apk would likely trip either method for a lot of OTAs though, since it's a pretty central component.
galaxyuserx said:
I use Galaxy s6 G9200 HK with Kernel compiled by me, but i have problem with root 5.1.1 and i think in future too 6.0
These root method is integrated in kernel source or i can integrate with those "boot.img systemless" my selfcompiled kernel?(repack boot.img with kernel compiled by me)
Is possible to work this new root method to android 5.1.1?
I have problem with gain root when i use kernel compiled by me ( STOCK kernel have too this problem BOOTLOOPs and FREEZEs on boot system) and i don't know how slove it :/
I found on chineese forums root integrated in boot.img it working good and isn't comunicat "KERNEL is not SEandroid enforced" but when i try integrate my kernel with this boot.img error with boot system :/
Click to expand...
Click to collapse
Yup, it's all ramdisk changes so should be workable on any version of Android. Chainfire left instructions outlining the ramdisk changes in the WIP thread if you want to give it a try.
phishfi said:
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of on the Nexus 6!!
Click to expand...
Click to collapse
Yup, seems to be the case with most banking and root-detecting apps... for now.
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
secguy said:
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
Click to expand...
Click to collapse
Just ran it and it passed.
Went ahead and installed su on a stock nexus 5, so far working well, android pay does not work but that was me being stupid and changing the host file and dpi before setting it up
I do notice a little input lag after this, not enough to even make me consider removing root, but it is noticeable, anybody else with this?
Hi all,
Just bought a shiny new Mi Mix for use in the UK.
I have installed UK google play and Android Pay but frustratingly it doesn't want to work.
"Android pay cannot be used on this device. This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM. As a result, Google can't confirm that your device meets Android pays security standards"
The device is not rooted.
Has anyone else found a fix ?
Grateful for any help!!
Not rooted, but does it have an unlocked Bootloader?
My import from China worked with Android Pay (and Barclays Pay) in the UK when I first bought it, but having unlocked the bootloader to put the EU Rom onto it, Android Pay no longer works, with the exact same message.
Oddly, Barclays still works fine.
TBH, Android Pay hardly worked with any of my cards, so I wasn't THAT concerned anyway. Still use my iPhone for most contactless stuff as all my cards work with that system.
rhug1802 said:
Hi all,
Just bought a shiny new Mi Mix for use in the UK.
I have installed UK google play and Android Pay but frustratingly it doesn't want to work.
"Android pay cannot be used on this device. This may be because your device is rooted, has an unlocked bootloader or is running a custom ROM. As a result, Google can't confirm that your device meets Android pays security standards"
The device is not rooted.
Has anyone else found a fix ?
Grateful for any help!!
Click to expand...
Click to collapse
greatcapp said:
Not rooted, but does it have an unlocked Bootloader?
My import from China worked with Android Pay (and Barclays Pay) in the UK when I first bought it, but having unlocked the bootloader to put the EU Rom onto it, Android Pay no longer works, with the exact same message.
Oddly, Barclays still works fine.
TBH, Android Pay hardly worked with any of my cards, so I wasn't THAT concerned anyway. Still use my iPhone for most contactless stuff as all my cards work with that system.
Click to expand...
Click to collapse
It maybe if you relock the bootloader it will work, check if bootloader is unlocked.
"fastboot oem device-info"
Think it will only work on Chinese stable.
I'm not that fussed with Android Pay not working - Barclays does, and Android Pay didn't work on all but 1 of my cards.
Also having used the EU ROM, I wouldn't go back to Chinese version.
Hopefully OP might find it helpful though.
Flash the official china ROM. The one that you have are unofficial ROM (if I can't say fake rom).
Seems to be working on mine, official china rom.
I'm on the official Global Rom and locked my bootloader. The app will finally allow me to add credit cards no problem. But the app won't launch or pay for anything near a terminal that accepts android pay. I unlock the phone, hold it to next to the terminal and nothing.
Anyone else have success on paying for anything?
Thorin78 said:
I'm on the official Global Rom and locked my bootloader. The app will finally allow me to add credit cards no problem. But the app won't launch or pay for anything near a terminal that accepts android pay. I unlock the phone, hold it to next to the terminal and nothing.
Anyone else have success on paying for anything?
Click to expand...
Click to collapse
I had this when i set up my bank card to use with the underground. You have to go to NFC section and change "Secure element position" to using HCE wallet.
Tokarin said:
I had this when i set up my bank card to use with the underground. You have to go to NFC section and change "Secure element position" to using HCE wallet.
Click to expand...
Click to collapse
Thanks. I've switched it over from embedded secure element to this and will give it a shot.
So after the latest Global Rom update, 8.2.5.0 MAHMIDL, android pay is broken again. NFC activates, vibrates, but i can't get it to process anything. it just keeps looping.
Is anyone else having this problem? I also uninstalled and reinstalled the android pay app. Thanks.
Thorin78 said:
So after the latest Global Rom update, 8.2.5.0 MAHMIDL, android pay is broken again. NFC activates, vibrates, but i can't get it to process anything. it just keeps looping.
Is anyone else having this problem? I also uninstalled and reinstalled the android pay app. Thanks.
Click to expand...
Click to collapse
You need to check whether it passes the safety net check. I've used stock rom with android pay before and it always fails after a rom update.
Leechoonhwee said:
You need to check whether it passes the safety net check. I've used stock rom with android pay before and it always fails after a rom update.
Click to expand...
Click to collapse
It passed. I also got an android pay update yesterday so I'll find out next time I use it again. Ugh.
Yup, still doesn't work. I've removed the credit card and added it back no problem. But whenever I use android pay to actually pay for something, i just get a rotating circle that doesn't seem to want to connect to a server I'm guessing.
Exactly the same here. Have tried everything. Currently I am on a developer rom. It doesn't work. Got a mi6 2 weeks ago and it is a similar story. Android pay works at all 7/11 as it seems but nowhere else. Drives me crazy. It is really too bad. Wish I could just use the NFC feature both phones have. Based out of Singapore btw.
Inster05 said:
Exactly the same here. Have tried everything. Currently I am on a developer rom. It doesn't work. Got a mi6 2 weeks ago and it is a similar story. Android pay works at all 7/11 as it seems but nowhere else. Drives me crazy. It is really too bad. Wish I could just use the NFC feature both phones have. Based out of Singapore btw.
Click to expand...
Click to collapse
I contacted google and they asked me to send them a report, but it looks like Xiaomi disabled this option in their build of the Global ROM. I'm lost and not sure what to do. Maybe I should install android pay from 3 versions ago and see if that helps.
Also, I can't ever get my Region to be anything other than Poland while I'm in the US. There are a bunch of other tiny issues that I've reported bugs about but Xiaomi seems to ignore.
Just paid for my breakfast with Android pay. On Resurrection Remix, dragonxia kernel, and I flashed the universal Xiaomi safetynet fix for Magisk. Go to Magisk settings, enable magiskhide, reboot, and safetynet passed.
Greetings from germany,
a buddy of mine got a Note 8 from a shady seller and it turned out that it had a custom rom:
Basisbandversion: N950FXXU1AQHB
Kernel-Version: 4.4.13-theGreatDream-v1.0.0
[email protected] #1
But he couldn't do any updates with it and quite a few apps didn't work because they said: "device is rooted and because of security policy etc..." (crudely translated from german)
such as the samsung and banking apps.
So we tried to go with the guide on how to flash and restore the device to stock firmware with odin.
For that i downloaded the N950FXXU1AQH9 version which is for the region germany and that seemed to be the most reasonable choice in the vast variety of approx. 200 available versions.
We did everything exactly as described in the guide and everything seemed to work perfectly. Updates were working again and also the banking app worked.
But the day after he wanted to try the Samsung Health app and it reported to not work because "security policy, can't open on a rooted device" (crudely translated from german again)
and others like the banking app also stopped working and reported the same.
Although we installed the N950FXXU1AQH9 version it now says in the softwareinformation that N950FXXU2BQKG is installed Oo
Strangely he also tried some apps to root/unroot like superSU etc. and they all told him "your device isn't rooted"
So regular apps tell "can't work because device is rooted" and root apps tell "can't unroot because device isn't rooted"
So i ask humbly: where is the error in this mess? What shall we do to make this device into a perfectly funtioning unrooted freshly fabricated note 8 again?
Thanks in advance
puzzlednerd said:
Greetings from germany,
a buddy of mine got a Note 8 from a shady seller and it turned out that it had a custom rom:
Basisbandversion: N950FXXU1AQHB
Kernel-Version: 4.4.13-theGreatDream-v1.0.0
[email protected] #1
But he couldn't do any updates with it and quite a few apps didn't work because they said: "device is rooted and because of security policy etc..." (crudely translated from german)
such as the samsung and banking apps.
So we tried to go with the guide on how to flash and restore the device to stock firmware with odin.
For that i downloaded the N950FXXU1AQH9 version which is for the region germany and that seemed to be the most reasonable choice in the vast variety of approx. 200 available versions.
We did everything exactly as described in the guide and everything seemed to work perfectly. Updates were working again and also the banking app worked.
But the day after he wanted to try the Samsung Health app and it reported to not work because "security policy, can't open on a rooted device" (crudely translated from german again)
and others like the banking app also stopped working and reported the same.
Although we installed the N950FXXU1AQH9 version it now says in the softwareinformation that N950FXXU2BQKG is installed Oo
Strangely he also tried some apps to root/unroot like superSU etc. and they all told him "your device isn't rooted"
So regular apps tell "can't work because device is rooted" and root apps tell "can't unroot because device isn't rooted"
So i ask humbly: where is the error in this mess? What shall we do to make this device into a perfectly funtioning unrooted freshly fabricated note 8 again?
Thanks in advance
Click to expand...
Click to collapse
I think that once rooted and Knox has been triggered the banking apps and certainly Samsung Pay will never work! I'm not thinking of rooting my SM-N9500 (I don't think I can anyway as it's Snapdragon), I used to root to get rid of adverts but Samsung have an app for that!
Sent from my SM-N9500 using Tapatalk
Once KNOX hasa been tripped its a can't be restored... You might b able to trick some of the apps into working by using a custom kernel but secure folder and KNOX are gone like the dinosaurs...
You should be able to find out about the custom kernels & how to flash by doing some reading.
robmeik said:
I think that once rooted and Knox has been triggered the banking apps and certainly Samsung Pay will never work! I'm not thinking of rooting my SM-N9500 (I don't think I can anyway as it's Snapdragon), I used to root to get rid of adverts but Samsung have an app for that!
Sent from my SM-N9500 using Tapatalk
Click to expand...
Click to collapse
I agree with this, I know that once rooted, some apps will not work anymore on that particular device, regardless of what you will plan on doing with that device.
knox is tripped.
the phone has most likely been successfully unrooted, but rooting it permanently makes alterations to a chip on the motherboard.
some apps will never trust this phone again, unless you can hide the knox fuse status.
so to get full use of the phone again you'll have to root it again and look into some root hiding apps/mods.
unfortunately I can't help you any further with that, I haven't rooted a knox-enabled device since the note 2.
Firstly thanks for all the enlightening answers. Now we are getting a bit closer.
I have just started with those topics on modding (rooting) of smartphones a few days ago and none of the guides i read mentioned anything about knox.
But yeah everything is gonna be more complex than anticipated. I will have to start digging deeper into this matter and try out a lot more of modded kernels and root hiding tools etc. to restore funtionality.
I will keep you updated on my progress... or lack of it :]
puzzlednerd said:
On another matter: The guy that "sold" my buddy this Note 8 seemed to be very eager to give it to him. At first he made an offer on local ebay and said that he didn't want his note 8 because it is rooted and modded etc.
My buddy made an agreement with him to exchange his older less worth samsung, which was all original and unrooted, for the sellers note 8. The seller complied although the difference in worth was approx. 250 Euro.
My buddy was happy that he made great deal... at first...
Later we found out that the same seller is selling my buddies old phone on local ebay again and surprise surprise it's rooted and modded again and offered for a much smaller price than what it's worth.
Now... is it possible to root and hack those phones with lets say... keyloggers and give them to unsuspected customers that enter all their account data and banking information?
Otherwise i have no idea why this seller is practically almost giving them away for nothing and is rooting formerly unrooted devices and sells them with the point that he doesn't want rooted devices and losing money with every trade.
Scam detected? What do you think?
Click to expand...
Click to collapse
we think it does not belong here. create your own thread on another forum and the topic of speculation-conspiracy
Then please pardon me dear sir. above part moved to offtopic:
https://forum.xda-developers.com/general/off-topic/scam-detected-topic-speculation-t3740922
Has anyone been able to get android pay working after flashing 8.0 firmware and rooting? If so could you talk through how you did it?
bot_rosco said:
Has anyone been able to get android pay working after flashing 8.0 firmware and rooting? If so could you talk through how you did it?
Click to expand...
Click to collapse
I have working Android Pay with Android One stock rooted firmware. I'm running the XT1900-1 Retail Edition. What have you done so far?
Sent from my moto x4 using Tapatalk
@jiggyman - Are you on Nougat or Oreo?
Neffy27 said:
@jiggyman - Are you on Nougat or Oreo?
Click to expand...
Click to collapse
I'm running the Android One Oreo firmware.
Sent from my moto x4 using Tapatalk
Just today a new magisk update was released which has allowed me to use Google pay . Anyone else who has been having issues and is using root (magisk) ensure you are using version 16
I OTA'd to 8.0 (I have the X4 Retail/Non-Fi version) and Android Pay is broken. It was working just fine on Nougat. Any pointers? TIA.
smmankad said:
I OTA'd to 8.0 (I have the X4 Retail/Non-Fi version) and Android Pay is broken. It was working just fine on Nougat. Any pointers? TIA.
Click to expand...
Click to collapse
Are you using Magisk for your root? If not, that's what you need. So remove your other root method like SUPERSU or whatever, then use the systemless root like magisk.
It is working for me.
edufur said:
Are you using Magisk for your root? If not, that's what you need. So remove your other root method like SUPERSU or whatever, then use the systemless root like magisk.
It is working for me.
Click to expand...
Click to collapse
Thank you - I was considering Magisk, but I'm not rooted at all (I'm on stock, re-locked bootloader - I re-flashed stock after playing around with unlocking the bootloader, TWRP, etc.). Is it because of the re-flash? I am able to OTA successfully, but Root Checker says "CTS Profile Match: Failed" for Safety Net. I suspect that's the issue, but have no clue about solving it. Googling isn't much help either (all answers point to Magisk - I'm okay with that, if that's a guaranteed solution, as I'm dreading having to lose data when I unlock the bootloader to install TWRP and Magisk). I'm pretty certain I'm missing something as it looks as though I am one of the few whose Pay isn't working. I even tried the Fi ROM, with same problem (OTA works, but Pay doesn't. Same CTS Profile Match error). This issue is driving me insane (Everything else works great and I love this device!)
smmankad said:
Thank you - I was considering Magisk, but I'm not rooted at all (I'm on stock, re-locked bootloader - I re-flashed stock after playing around with unlocking the bootloader, TWRP, etc.). Is it because of the re-flash? I am able to OTA successfully, but Root Checker says "CTS Profile Match: Failed" for Safety Net. I suspect that's the issue, but have no clue about solving it. Googling isn't much help either (all answers point to Magisk - I'm okay with that, if that's a guaranteed solution, as I'm dreading having to lose data when I unlock the bootloader to install TWRP and Magisk). I'm pretty certain I'm missing something as it looks as though I am one of the few whose Pay isn't working. I even tried the Fi ROM, with same problem (OTA works, but Pay doesn't. Same CTS Profile Match error). This issue is driving me insane (Everything else works great and I love this device!)
Click to expand...
Click to collapse
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
The funny thing is that the re-flash was done using 7.1.1 stock ROM found here - https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/ (I used the 26.83-34-0-1 and then OTA'd up to 8.0/March 2017 from there). Pay was working on 7.1.1. Right after the last 8.0 OTA, it broke. I used the standard fastboot flash and flashed all files in the right order. What stumps me is that there was no issue in 7.1.1... Only after OTA did it break. Can you point me to the ROM I should use just to make sure I didn't pick a bad one? (I tried so many in my attempt to solve this that I really need a second set of eyes to tell me if I'm going wrong somewhere).
---------- Post added at 03:32 AM ---------- Previous post was at 03:17 AM ----------
edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
PS: Also, is there a way I can start from a clean slate, I mean, phone ? Some way I can do a hard wipe and then flash stock? I'm sure something is mucked up currently, so a clean flash would be best.
edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
My investigation here: https://forum.xda-developers.com/mo...ware-stock-7-1-1-t3693145/page13#post76610643
Hi I've been using a custom rom for quite some time now but I decided to go back to stock as I don't really see the benefits.
the issue I'm having is despite flashing a stock rom in Odin and seemingly completely unrooting the device, apps like google pay aren't allowing me to use them as they say the device has been rooted or modified in some way.
in the settings it clearly says my device is official status, does anyone know how to overcome this issue please? I prefer to use google pay to my cards as I often lose them if I take them out
thanks
Drizzy xS said:
Hi I've been using a custom rom for quite some time now but I decided to go back to stock as I don't really see the benefits.
the issue I'm having is despite flashing a stock rom in Odin and seemingly completely unrooting the device, apps like google pay aren't allowing me to use them as they say the device has been rooted or modified in some way.
in the settings it clearly says my device is official status, does anyone know how to overcome this issue please? I prefer to use google pay to my cards as I often lose them if I take them out
thanks
Click to expand...
Click to collapse
well it was probably written in every thread when you downloaded twrp and followed the guide to root that this was going to happen. its pretty wide spread knowledge if you'd care to have investigate a bit before jumping ship. been like this for years and years so nothing new or "hidden".
reading goes a long way. even now if you'd have taken a minute to investigate you'd see the futility of what you want to accomplish. ( going to stock and expecting it to be as it once was before knox was tripped)
moreover there are guides on how to hide google pay and installing a version that does not detect root or a modified system.
search is your friend.
edit
there is one thing that i just though of that you might have forgotten to do and just might work though.
during the rooting/twrp process you had to go to dev options and toggle the OEM unlock.
go there and lock back OEM. this will wipe device so beware.
also when you fully flashed back the 4 md5 files with odin, was data wiped?