My phone is un-rooted but I'm getting a CTS Profile match fail when running a safetynet test. Can anyone guide me on how to resolve this error?
biglo said:
My phone is un-rooted but I'm getting a CTS Profile match fail when running a safetynet test. Can anyone guide me on how to resolve this error?
Click to expand...
Click to collapse
There is a "Pass SafetyNet" section in this guide.
Lughnasadh said:
There is a "Pass SafetyNet" section in this guide.
Click to expand...
Click to collapse
I've seen this but I doesn't say how I can pass safetynet without being rooted.
biglo said:
I've seen this but I doesn't say how I can pass safetynet without being rooted.
Click to expand...
Click to collapse
I'm assuming you have your bootloader unlocked? If so, that's why you don't pass SafetyNet. You'll have to root and use at least the USNF mod to pass. Or else make sure you are completely stock and lock your bootloader.
Lughnasadh said:
I'm assuming you have your bootloader unlocked? If so, that's why you don't pass SafetyNet. You'll have to root and use at least the USNF mod to pass. Or else make sure you are completely stock and lock your bootloader.
Click to expand...
Click to collapse
Actually there is a kernel mod that will allow unlocked bootloader to pass. It's incorporated with ProtonAosp but stand alone too. Pretty sure not 100
Related
Well, I'm rooted. But, I've bypassed that.
The only problem I'm having is an error that reads: "Isis is unable to download the Terms of Service at this time. Please make sure you are connected to the Internet." I can't find any record on this error on Google or XDA
So, if someone could make an account for me (with my name and email and a temp pass and stuff), I'd be eternally grateful
Something else is going on there,custom rom? I believe if using wifi have to use cell connection
Wonders_Never_Cease said:
Something else is going on there,custom rom? I believe if using wifi have to use cell connection
Click to expand...
Click to collapse
Stock ROM, just rooted. I have tried Wifi Off, with cell connection and with wifi. Both produce the same error.
Possibly the isis server is having issues...which mod did you use to bypass isis borking on rooted devices?
Wonders_Never_Cease said:
Possibly the isis server is having issues...anything is possible....
Click to expand...
Click to collapse
It's been doing it ever since I originally tried a week ago...I figure once I have an account made, I can login. It allows me to attempt to login just fine. Obviously I don't have proper credentials.
Create an account on their site maybe...no clue as I dont use isis
Wonders_Never_Cease said:
Create an account on their site maybe...no clue as I dont use isis
Click to expand...
Click to collapse
Sadly, it has to be done from a phone. None of my friends have a phone compatible with it, either. :/
which mod did you use to bypass isis borking on rooted devices? Theres a flashable zip and rootcloaker via xposed framework
Wonders_Never_Cease said:
which mod did you use to bypass isis borking on rooted devices?
Click to expand...
Click to collapse
This one: http://forum.xda-developers.com/showthread.php?t=2425346
it has seemed to work for other M8 users.
Uninstall that....Use Xposed feamework and rootcloak module,know for a fact it works 100%
Bammeh said:
This one: http://forum.xda-developers.com/showthread.php?t=2425346
it has seemed to work for other M8 users.
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Uninstall that....Use Xposed feamework and rootcloak module,know for a fact it works 100%
Click to expand...
Click to collapse
That's what I currently have. Same situation.
Tried the ISIS Bypass first, it bypassed root but gives me the error. Uninstalled and rebooted. Then installed RootCloak and rebooted, and i get the same error.
Me personally id factory reset and start over and use the xposed first after rooting
Wonders_Never_Cease said:
Me personally id factory reset and start over and use the xposed first after rooting
Click to expand...
Click to collapse
Haha, it's not all that important. That is a lot of work. Id rather just see if someone can make an account for me
I have the same error on a device running 4.0.4 (not rooted). Perhaps this is a version check and pre-4.4 will fail?
What I Did
1. I flashed the decrypt kernel for the N Beta through ADB
2. I did a factory reset to finish the decrypt process
3. I booted into TWRP using ADB (I did it this way to keep stock recovery, you can just flash TWRP if you like)
4. Once in TWRP, though ADB I typed "ADB Shell"
Then typed "echo SYSTEMLESS=true>>/data/.supersu"
Followed by "echo BINDSYSTEMXBIN=false>>/data/.supersu"
5. I proceeded to flash the latest Supersu Beta
6. Set up Android Pay and profit!
It is pretty much the exact process for Android Pay with Systemless root, but you do HAVE to have decrypted or else this will not work.
Screenshots or It Didn't Happen
Do you mind linking the decrypt kernel?
it simply works if you are stock and systemless rooted.
trebills said:
Do you mind linking the decrypt kernel?
Click to expand...
Click to collapse
No problem
http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
MrKaon said:
it simply works if you are stock and systemless rooted.
Click to expand...
Click to collapse
Yes exactly, but for now, there is no way to root unless you decrypt first
kingmikel said:
No problem
http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Yes exactly, but for now, there is no way to root unless you decrypt first
Click to expand...
Click to collapse
I'm running the same setup but with Adaway and ElementalX Kernel. I was able to pay for coffe this morning
omf05 said:
I'm running the same setup but with Adaway and ElementalX Kernel. I was able to pay for coffe this morning
Click to expand...
Click to collapse
I'm still trying to get Adaway to work! And how's ElementalX running with the new preview? I have not tried it yet
kingmikel said:
I'm still trying to get Adaway to work! And how's ElementalX running with the new preview? I have not tried it yet
Click to expand...
Click to collapse
ElementalX is running fine for me so far, just use the version for DP2 and you should be fine..
I am system rooted with BusyBox and V4A installed and SELinux permissive on DP3. I haven't tested Android Pay, but I was able to add a card without a problem. Is that indicative that it should work? I had the opportunity to test it today but didn't.
Nitemare3219 said:
I am system rooted with BusyBox and V4A installed and SELinux permissive on DP3. I haven't tested Android Pay, but I was able to add a card without a problem. Is that indicative that it should work? I had the opportunity to test it today but didn't.
Click to expand...
Click to collapse
From my experience, if you successfully add a card then it works. Usually prevent you from adding a card. I also use Safetynet Helper Sample and make sure it passes
kingmikel said:
From my experience, if you successfully add a card then it works. Usually prevent you from adding a card. I also use Safetynet Helper Sample and make sure it passes
Click to expand...
Click to collapse
Fails the CTS check. I guess only way to know if to go try it out lol.
Nitemare3219 said:
Fails the CTS check. I guess only way to know if to go try it out lol.
Click to expand...
Click to collapse
Mine passes lol. I'm confused as to why it let you add a card!
kingmikel said:
Mine passes lol. I'm confused as to why it let you add a card!
Click to expand...
Click to collapse
Guy in the N development thread showed AP working for him and he is system rooted as well. Probably a bug... but it'd be nice if Google were allowing rooted users to use AP since they know we find workarounds anyway.
Nitemare3219 said:
Guy in the N development thread showed AP working for him and he is system rooted as well. Probably a bug... but it'd be nice if Google were allowing rooted users to use AP since they know we find workarounds anyway.
Click to expand...
Click to collapse
That guy was me. Passes safety net fine. All I did was root and added the card. Not sure probably a bug that will be fixed. Until then I'll enjoy not having to make any extra steps.
Don't like me......... BITE ME!!!
Nitemare3219 said:
Fails the CTS check. I guess only way to know if to go try it out lol.
Click to expand...
Click to collapse
Mine fails the step on N Beta 1 with systemless root. I haven't tried using pay though but I do have a card added.
Let me know if you try it and have success.
It is possible flash a custom kernel and still have Android pay working?
Enviado desde mi 6P
negrata said:
It is possible flash a custom kernel and still have Android pay working?
Enviado desde mi 6P
Click to expand...
Click to collapse
It works with current and prior Pure Nexus (MTC19T). Lately, I have flashed the FiFix_ Google Dialer zip (as noted by Beanstown) after the other steps to make Android Pay work. Using it on Rooted N now but just came from Pure Nexus.
Sent from my Nexus 6P using XDA-Developers mobile app
I am using lineage os 14.1 latest build and my phone is not rooted, magisk is not installed, still getting cts profile mismatch. Any help?
Unlocked bootloader.
arnabbandopadhyay said:
I am using lineage os 14.1 latest build and my phone is not rooted, magisk is not installed, still getting cts profile mismatch. Any help?
Click to expand...
Click to collapse
How you did that?
BCasS said:
How you did that?
Click to expand...
Click to collapse
Using root checker app from play store
arnabbandopadhyay said:
I am using lineage os 14.1 latest build and my phone is not rooted, magisk is not installed, still getting cts profile mismatch. Any help?
Click to expand...
Click to collapse
You need to install magisk and enable hide root... Officials
lineage will never pass the cts mismatch since bootloader is unlocked. Also in the google play ur device shows as uncertified in ur case..
hasan4791 said:
You need to install magisk and enable hide root... Officials
lineage will never pass the cts mismatch since bootloader is unlocked. Also in the google play ur device shows as uncertified in ur case..
Click to expand...
Click to collapse
Thanks
So I am a regular user of Snapchat but after I rooted my phone I can't log in to Snapchat. I think it is because of SafetyNet. The check from Magisk tells me my basicIntegrity is alright buy my ctsProfile isn't, any tips?
pim8181 said:
So I am a regular user of Snapchat but after I rooted my phone I can't log in to Snapchat. I think it is because of SafetyNet. The check from Magisk tells me my basicIntegrity is alright buy my ctsProfile isn't, any tips?
Click to expand...
Click to collapse
Which Magisk version have you installed?
kilroystyx said:
Which Magisk version have you installed?
Click to expand...
Click to collapse
I already fixed it on my own, thanks nonetheless.
So I purchased an A217M yesterday and first thing I tried to do was try and root it
I followed this guide https://magiskapp.com/root-samsung-galaxy-a21s-using-magisk/
and I *think* I successfully managed to do it cause I didn't get any bootloops
to verify that I was indeed in root mode I reinstalled magisk but the app said something like "Additional steps are required for magisk to work properly" or something then took me to a screen that said select something something and the other option was direct install, I picked direct install and now when I try to boot it says "Only official released binaries are allowed to be flashed" in a corner of the screen and now I'm stuck here. Is there any way to reverse this?
"the here we go again" part means I also screwed up the previous time I tried to root a phone lol, on that occasion tho it was because I deleted an essential app accidentally
have a look anon
I don't wanna mess around with it too much before someone replies to but would doing a Factory data reset again fix this? I got work tomorrow and I only have today to get this working. I also wanna sell this other phone I have asap
REFLASH THE FIRMWARE
Arthursmithlik said:
REFLASH THE FIRMWARE
Click to expand...
Click to collapse
you mean I just gotta do the whole odin thing again?
"An error has occurred while updating the device software"
it cant even be turned off now
alright, now its stuck in setup connection and there's a white loading bar below.... rip?
ok so I held down volume down + power. the screen turned off for a sec and now the bar is gone, still stuck in the same screen tho
xalcor said:
you mean I just gotta do the whole odin thing again?
"An error has occurred while updating the device software"
it cant even be turned off now
Click to expand...
Click to collapse
btw I used the same Odin 3 steps I found in the magisk guide
guess this is Samsung's equivalent to bsod then..
why would magisk do this to me
welp
no response so I guess I'm stuck here
... at times like this I really wish I could go back in time
aight, left it with a buddy so he could redo everything from scratch using his box thingy. At least it can be saved. 25 bucks for it tho :v
After this show I really don't feel like paying $25 more in case I end up bricking this thing again. Anyone who has successfully managed to root the phone, please tell me how you did.
Reminder: Model is SM-A217M/DS and is running Android 12
xalcor said:
After this show I really don't feel like paying $25 more in case I end up bricking this thing again. Anyone who has successfully managed to root the phone, please tell me how you did.
Reminder: Model is SM-A217M/DS and is running Android 12
Click to expand...
Click to collapse
We do not allow multiple posts on the same topic, therefore I have moved your post into this thread.
Additionally, do not use profanity on XDA.
Assuming you've already unlocked your bootloader, the easiest way would be to flash a custom recovery such as TWRP, then install Magisk in the custom recovery.
However, seeing as TWRP is not available for the A21S, you'd want to patch the AP.tar file in Magisk, then flash in Odin. See the official Magisk installation guide here.
V0latyle said:
We do not allow multiple posts on the same topic, therefore I have moved your post into this thread.
Additionally, do not use profanity on XDA.
Assuming you've already unlocked your bootloader, the easiest way would be to flash a custom recovery such as TWRP, then install Magisk in the custom recovery.
However, seeing as TWRP is not available for the A21S, you'd want to patch the AP.tar file in Magisk, then flash in Odin. See the official Magisk installation guide here.
Click to expand...
Click to collapse
I thought it was fine since it auto-censors but alright
also it says here that using magisk here will "trip" knox. what does this mean exactly?
Sorry if it's a newbie question (I am a noob still )
xalcor said:
I thought it was fine since it auto-censors but alright
also it says here that using magisk here will "trip" knox. what does this mean exactly?
Sorry if it's a newbie question (I am a noob still )
Click to expand...
Click to collapse
Modified binaries trip Knox. Don't worry about it
steps 4 and 9 are a bit confusing, what is boot ramdisk and how do I know if my device has it
sorry again, I really don't wanna screw this up. I'm thin on money and gotta pay for important stuff this week
V0latyle said:
Modified binaries trip Knox. Don't worry about it
Click to expand...
Click to collapse
xalcor said:
you mean I just gotta do the whole odin thing again?
"An error has occurred while updating the device software"
it cant even be turned off now
Click to expand...
Click to collapse
its fast
xalcor said:
steps 4 and 9 are a bit confusing, what is boot ramdisk and how do I know if my device has it
sorry again, I really don't wanna screw this up. I'm thin on money and gotta pay for important stuff this week
Click to expand...
Click to collapse
Check in magisk app
Tripping know simply disables samsung pay, secure folder, and a few other apps. It has probobly already been tripped when you tried to boot. A lot of this can be fixed by modules and such after getting root. Tripping knox persists even after going stock though.
Read xda’s guide.