I'm wanting to only unlock bootloader, but otherwise keep everything stock. Will just unlocking bootloader invalidate CTS checks and deny things like Android Pay?
I also want to keep getting OTAs, keep stock recovery and remain rootless. I just know I'll eventually want to root, but i don't want to be forced to wipe when I do
NOTE: I get my 6T in a few hours
I use Android Pay all the time with my unlocked and rooted 6T. If you end up installing things that mess with the system partition and SafetyNet like Xposed then Android Pay will not work.
So just the act of unlocking the bootloader will not disable Android Pay in my experience with my 5T and 6T now.
It was basically the same for me. I just tested it for you and Google Pay seemed to work fine. I do know from the DRM Info app that my security level went from L1 to L3, which I guess means no HD video on sites like Netflix or whatever, which I don't use on my phone anyway. That's about all I know so far
Thanks guys! Super appreciate it! I remember seeing posts about people just unlocking bootloaders on other devices causing issues, I didn't think it would. Gives me a great peace of mind before I do something silly!
Magisk will keep SafetyNet valid.
If you're unlocked but NOT rooted, you'll need to use a custom kernel.
If you have an unlocked bootloader without Magisk and without a custom Kernel, you will fail CTS and in turn fail SafetyNet.
Oh no. Unlocked bootloader, ran an update and got the attached images.
Looks like unlocking the bootloader kills off Google Pay and CTS
@hartleyshc seems to be correct. Might have to lock it again
mattisdada said:
Oh no. Unlocked bootloader, ran an update and got the attached images.
Looks like unlocking the bootloader kills off Google Pay and CTS
@hartleyshc seems to be correct. Might have to lock it again
Click to expand...
Click to collapse
I'm not currently rooted on any device,but,shouldn't using Magisk fix what you're concerned about? (At least in relation to this particular phone).
The one reported thing w/unlocking the b/l is Widevine Level 1 is downgraded to Level 3,preventing video playback at HD quality on some streaming content.
AFAIK,there is no Magisk or Xposed module that fixes DRM on b/l unlocked phones.
That's been shown to be the case with this phone,YMMV if this is an issue to you:
https://android.gadgethacks.com/how...ix-amazon-prime-video-other-services-0181603/
Here's the app to check/verify:
https://android.gadgethacks.com/how...ix-amazon-prime-video-other-services-0181603/
KOLIOSIS said:
I'm not currently rooted on any device,but,shouldn't using Magisk fix what you're concerned about? (At least in relation to this particular phone).
The one reported thing w/unlocking the b/l is Widevine Level 1 is downgraded to Level 3,preventing video playback at HD quality on some streaming content.
AFAIK,there is no Magisk or Xposed module that fixes DRM on b/l unlocked phones.
That's been shown to be the case with this phone,YMMV if this is an issue to you:
https://android.gadgethacks.com/how...ix-amazon-prime-video-other-services-0181603/
Here's the app to check/verify:
https://android.gadgethacks.com/how...ix-amazon-prime-video-other-services-0181603/
Click to expand...
Click to collapse
Main thing I want is just Google Pay and certain games, Widevine I'm not terribly fussed about. Right now Google Pay is complaining after just unlocking bootloader, no other modifications
Magisk does fix it, but I'm trying to be more hands off now, I don't want to have to install something after each ota, do manual updates, etc
mattisdada said:
Main thing I want is just Google Pay and certain games, Widevine I'm not terribly fussed about. Right now Google Pay is complaining after just unlocking bootloader, no other modifications
Click to expand...
Click to collapse
Install and stay on the latest version of Magisk. If there's any apps that complain about being rooted, you can use Magisk to hide itself from that app. (Pokemon Go and banking apps seem to implement this most frequently).
Especially if you don't care about widevine, I'd suggest just rooting. It will be easier to install some sort of mod in the future than having to unlock your bootloader again.
Go into Magisk settings and toggle the options to download and install the latest beta of Magisk. That way you can always stay current and always pass SafetyNet.
I was rooted on my Nexus 6p and I can't remember the last time Magisk failed SafetyNet for me except when I wasn't current and I'm a very frequent Google Pay user.
hartleyshc said:
Magisk will keep SafetyNet valid.
If you're unlocked but NOT rooted, you'll need to use a custom kernel.
If you have an unlocked bootloader without Magisk and without a custom Kernel, you will fail CTS and in turn fail SafetyNet.
Click to expand...
Click to collapse
From what I understand if he has Magisk his device should be rooted. Since I have valid SafetyNet check with stock kernal. I would share my Magisk hide.
P.S. Make sure that "Logger buffer sizes" under "Development tools" is not "Off" otherwise Magisk hide will not be triggered.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
From what I understand if he has Magisk his device should be rooted. Since I have valid SafetyNet check with stock kernal. I would share my Magisk hide.
P.S. Make sure that "Logger buffer sizes" under "Development tools" is not "Off" otherwise Magisk hide will not be triggered. View attachment 4671491View attachment 4671492View attachment 4671493View attachment 4671494
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
SafetyNet check result.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
From what I understand if he has Magisk his device should be rooted. Since I have valid SafetyNet check with stock kernal. I would share my Magisk hide.
P.S. Make sure that "Logger buffer sizes" under "Development tools" is not "Off" otherwise Magisk hide will not be triggered.
Click to expand...
Click to collapse
But that's not what they asked. They said they only wanted to unlock the bootloader. You will fail safetynet that way.
Safetynet checks against unlocked bootloaders. There's currently two ways to bypass this check. With magisk, or with a custom kernel.
Also this thread was almost 2 months old. No need to bring it back up. Their question was answered.
Related
Has anyone received Google Assistant on their phones yet? Just curious.
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
I'm surprised to hear some people still don't have GA natively. I'm a long time HTC user, but I just bought my 10 last Fri. it's pretty sweet. although, I must say, I still REALLY like my One M8.
SilverZero said:
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
Click to expand...
Click to collapse
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
SilverZero said:
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
Click to expand...
Click to collapse
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
"OK Google" Always on!!??
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
misfiremind said:
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
Click to expand...
Click to collapse
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
this is from my Bolt, so it may be different, but I can disable just fine...
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
misfiremind said:
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
Click to expand...
Click to collapse
Ill try that but I flashed N using the RUU and then clean installed OMJ's badboys rom so no app data would have been there during M to N
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
OMJ said:
this is from my Bolt, so it may be different, but I can disable just fine...
Click to expand...
Click to collapse
Thats strange, i dont have all those menu entries... could be cause I have work email on my phone via activesync which restricts certain security and lockscreen options.
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
Click to expand...
Click to collapse
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
SilverZero said:
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
Click to expand...
Click to collapse
yes, merely having the bootloader unlocked even w/ 100% stock ROM, safetynet will fail....the beauty of magisk is that it hides it
I think at this point I'd rather relock my bootloader and go back to using my Galaxy S4 while I try to sell my HTC 10 and then put that money towards a Pixel. Anybody wanna buy a phone? ?
It's here! I literally just this minute got Google Assistant!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I think I am going to give this a shot. I am running your stock rooted with TWRP while S-on. Can I just install your Magisk Full Rom and go from there or is that too easy to believe? Thanks OMJ!
OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
Is magisk a ROM or more of a mod? And what is magisk su? I'm going to try and get my phone rooted this weekend but I can't find a tutorial thread, it seems to be scattered everywhere. It seems like I fastboot TWRP, flash SuperSU, flash magisk then install magisk manager from Google Play?
misfiremind said:
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
Click to expand...
Click to collapse
im running viper due to lack of cm/aosp st the moment.. so i have magisk but i have no idea what it is or how to use it. very little instruction out there.
Has anyone been successful in editing their build.prop file to activate (or deactivate) Google Assistant? I actually want to deactivate Google Assistant but I can't seem save changes to my build.prop file.
I have root on stock ROM.
Set SE Linux to permissive.
Tried using Root Explorer and build.prop Editor. Both give me an error message stating it can't save the build.prop file.
Suggestions?
In the last week I received my xperia x compact completely stock. First thing I do when I get a new phone before even activating it is root it. I was utilizing this guide to root my xperia x compact "Guide: Root + Custom Kernel + Clean rom + TA for X Compact" and I am stuck on the step where you are instructed to flash the modified XC-GenesisKernel-v1.04-nodrm kernel and SU. Flashing this kernel always results in a boot loop (Ive waited more then 30 minutes for it to resolve). I reflash the stock service exchange unit - 34.1.A.1.198 MM firmware to get back a functioning phone. The guide recommends:
"Run xperifirm and download the "service exchange unit - 34.1.A.1.198" firmware for posterity and latest rom for your region."
Am I supposed to use the most current nougat firmware for the following steps and only use the service exchange unit firmware if I need to downgrade to the lower original firmware? The thread for the XC-GenesisKernel states it is for nougat roms, which would explain a boot loop when I try to use the service exchange unit MM rom. Ideally Id like to stay on MM so that I can use xposed. Root and the phone being fully functional with no loss of camera and such is my main desire, xposed is secondary. I have a Backup TA of my DRM keys, the phone bootloader is unlocked, and I am looking for a little direction / clarification, any help in this respect is greatly appreciated.
Thanks
efaustus9 said:
help in this respect is greatly appreciated.
Click to expand...
Click to collapse
Click the first link in the guide and read it.
XperienceD said:
Click the first link in the guide and read it.
Click to expand...
Click to collapse
Thanks, I read through it and I see indeed the latest nougat firmware is what I should use in the later steps of tuten1000's guide and is the source of the boot loop I am experiencing.
If possible I would like to stay on marshmallow so I can used xposed framework. Are you aware of or can you recommend a kernel I can flash that will give me root, fingerprint, and use of most DRM functions while still on marshmallow.
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
itandy said:
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
Click to expand...
Click to collapse
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
efaustus9 said:
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
Click to expand...
Click to collapse
You're all good to begin with MM stock ROM.
itandy said:
You're all good to begin with MM stock ROM.
Click to expand...
Click to collapse
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
efaustus9 said:
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
Click to expand...
Click to collapse
This is a common request but the answer is no.
itandy said:
This is a common request but the answer is no.
Click to expand...
Click to collapse
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
efaustus9 said:
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
Click to expand...
Click to collapse
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
itandy said:
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
Click to expand...
Click to collapse
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
efaustus9 said:
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
Click to expand...
Click to collapse
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
itandy said:
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
efaustus9 said:
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
Click to expand...
Click to collapse
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
itandy said:
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
Click to expand...
Click to collapse
Great, I will definitely check out your app. Ideally Id like to mimic what I believe is called the "immersive mode" in supported apps. In this mode the app takes up the full screen and the icons are replaced with three persistent minimal dots.
As title said, what features im going to lose besides the OTA and knox?
Sent from my SM-G950F using Tapatalk
iiD4x said:
As title said, what features im going to lose besides the OTA and knox?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Caution: This phone has dm-verity enabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
gunner007dc said:
Samsung Pay if you use it (any Knox dependant apps), Android Pay can work with Magisk but it's a cat-mouse game of passing SafetyNet. Some financial apps will refuse to work on rooted phones (some can be avoided with Magisk Hide) but if they mean anything to you it's best to check the apps to see if anyone reports problems with a rooted device. I know Netflix and other content providers sometimes block rooted phones.
Click to expand...
Click to collapse
:good: Thanks.
Fusseldieb said:
Caution: This phone has dm-verity enabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
Click to expand...
Click to collapse
Yeah, i did backup before rooting, Thanks.
Warrenty
Pokemon go
Warranty (tripping knox), Android & Samsung Pay and over-the-air updates.
Generally you have to unroot for the OTA updates to work, but sometimes that is not enough, you have to factory restore the device as well. There is the app "FlashFire" which help you keep root as you upgrade OTA, but I find this won't work on all phones.
These three reasons are why I simply do not root anymore. Now if you have a Google Pixel or OnePlus, they generally don't take away your warranty even if you unlock bootloader or root. Some manufacturer like HTC and Moto, generally you have to request a bootloader unlocking code in order to install custom recovery to root, and in requesting the unlock code you forfeit your warranty.
Is there a way to patch s Health to get it working?
Fusseldieb said:
Caution: This phone has dm-verityenabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
Click to expand...
Click to collapse
The only thing you said that is correct is that the phones have dm-verity. But given that is implemented by the boot. Img, you can either remove it with 1, an engineering boot, because you can disable dm verity with selinux in permissive. 2, flash a rom that doesn't contain the dmverity flag, seeing as the boot only checks dm verity against the partitions that contain the flag(which isn't many. And is none on a full custom rom) or 3, pull apart the boot image and remove the dmverity file.
And general root has no bearing on dmverity anyways unless an app attempts to obtain root during boot up.
But anyways. It really depends on the root method as to what you lose. If we can achieve root with a locked bootloader, you will still be able to use Samsung pay and other Knox apps with standard root hider
Hi all is there a saver root yet every one I see there was problems
cheers
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
in theory according to posts ive seen for other devices you need magisks latest beta version.
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
Check by Playstore>settings... you're probably uncertified...
EDIT: You need magisk to pass the safetynet...
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
EVR_PR said:
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
Click to expand...
Click to collapse
It won't unless you either 1) Use magisk as mentioned or 2) use a custom kernel with SafeyNet patches.
When you unlock your bootloader, the prop (which you can read using a terminal emulator and typing getprop) has a flag called verifiedbootstate. If it returns anything but green SafeyNet will fail.
Sent from my OnePlus 3T using XDA Labs
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
gameofdroness said:
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
Click to expand...
Click to collapse
Of course..why not...
HatRiGt said:
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
Click to expand...
Click to collapse
I've flashed v. 13 (https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589) and worked as a charm!
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
oowaymike said:
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
Click to expand...
Click to collapse
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
yubimusubi said:
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
Click to expand...
Click to collapse
Thanks for the suggestions. I tried the stable version with no luck as well. I'll wait for the next beta version, and if that doesn't do the trick ill try reflashing the stock partition. If anyone finds a custom kernel that gets around safety net I'd really appreciate it.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Eric214 said:
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Click to expand...
Click to collapse
I don't know if this is OP'S reason, but you can boot TWRP without actually installing it... So you can take nandroid backups of an otherwise stock device.
Also, unlocking bootloader wipes your phone, so if you want it stock for now but think you might root in the future you won't have to deal with that...
TBH though, SafetyNet is working as advertised by failing an unlocked bootloader. We like to have our cake and eat it too.
Guys , how to unlock Mi A1 ?
Fine for me.
You have to tick it in the dev options
Edit: tap several times on the build number to unlock the dev options.
Have you used the GCam tool?
Just tap on Build Number until dev options activation, touch "allow OEM unlock) then reboot to fastboot and {fastboot oem unlock), if you lock the bootloader again you will lose all of your data.
After BL unlocking your phone will be uncertified (can't pass SafetyNet).
N1ck474 said:
After BL unlocking your phone will be uncertified (can't pass SafetyNet).
Click to expand...
Click to collapse
if i lock my bootloader , phone auto restart and erase data ... if i lock , phone data erase again . strange ..
You need to enable OEM unlocking in Developer options
JoKeRLeE said:
if i lock my bootloader , phone auto restart and erase data ... if i lock , phone data erase again . strange ..
Click to expand...
Click to collapse
This is expected behaviour in case you are unlocking. Becuase, when you unlock, your data will be in risks.
In some devices, it's implemented for locking as well.
InvalidDNA said:
This is expected behaviour in case you are unlocking. Becuase, when you unlock, your data will be in risks.
In some devices, it's implemented for locking as well.
Click to expand...
Click to collapse
seems like latest aboot implement it .
coremania said:
You have to tick it in the dev options
Edit: tap several times on the build number to unlock the dev options.
Click to expand...
Click to collapse
How install new font, please tell me
ozgurubuntu said:
How install new font, please tell me
Click to expand...
Click to collapse
U can use substratum, ifont app or magisk module
I use the Google sans mod magisk module.
How you flashed 8.1? Will OTA works after that?
Will the user data be erased by unlocking 8.1?
Wired Life said:
How you flashed 8.1? Will OTA works after that?
Will the user data be erased by unlocking 8.1?
Click to expand...
Click to collapse
User data still here until the bootloader still unlocked (so, with this ROM, don't lock it)
OTAs doesn't work.
Flash it with TWRP, just flash from stock April Oreo, no wipes.
N1ck474 said:
...After BL unlocking your phone will be uncertified (can't pass SafetyNet).
Click to expand...
Click to collapse
Not really. I have unlocked my bootloader and have'nt got any problems with SafetyNet. When I check it on magisk It passes with no issues. Also I'm able to use banking apps with no issues.
Takeawake said:
Not really. I have unlocked my bootloader and have'nt got any problems with SafetyNet. When I check it on magisk It passes with no issues. Also I'm able to use banking apps with no issues.
Click to expand...
Click to collapse
Then i don't know where's the problem on my phone, with leaked 8.1 and unlocked BL it's uncertified
N1ck474 said:
Then i don't know where's the problem on my phone, with leaked 8.1 and unlocked BL it's uncertified
Click to expand...
Click to collapse
If you have Xposed you will never pass SafetyNet either. But you need up to date Magisk at least.
CosmicDan said:
If you have Xposed you will never pass SafetyNet either. But you need up to date Magisk at least.
Click to expand...
Click to collapse
I have latest Magisk just for the GCam Module...
Probably because you installed xposed.. I did too and finally I reflashed the ROM to avoid the SafetyNet problem. With xposed allways will get fail on SafetyNet test since It modifies the system partition. Magisk don,nt.
Takeawake said:
Probably because you installed xposed.. I did too and finally I reflashed the ROM to avoid the SafetyNet problem. With xposed allways will get fail on SafetyNet test since It modifies the system partition. Magisk don,nt.
Click to expand...
Click to collapse
I don't have xposed
N1ck474 said:
I don't have xposed
Click to expand...
Click to collapse
Hummm... Then u can try this
https://forum.xda-developers.com/showthread.php?t=3722565