No Magisk trigger safety net? - Google Pixel 2 Questions & Answers

So I'm on Android DP4 and I didn't install magisk or anything and Snapchat is failing I can't download Netflix and nothing's quite working so I guess they just trigger the safety net for just being on a developer preview? Like on DP3 I could still.use Snapchat just fine this one won't let me log in just keeps saying my password is wrong

You presumably have an unlocked bootloader. Have you flashed a custom kernel? You'll need one which has patched the something-something. All custom kennels do. I don't know if there are custom kernels that are compatible with DP4 yet but I suspect there are. Try flashing one and then checking if safety net still fails.

AaronGavin said:
So I'm on Android DP4 and I didn't install magisk or anything and Snapchat is failing I can't download Netflix and nothing's quite working so I guess they just trigger the safety net for just being on a developer preview? Like on DP3 I could still.use Snapchat just fine this one won't let me log in just keeps saying my password is wrong
Click to expand...
Click to collapse
Google had to fix their end. It's fixed.
Sent from my Pixel 2 using Tapatalk

Related

Aokp , aosp

Hi guys.
When trying to use these type of ROMS I get one BIG problem. A program that uses BANK ID , when logging in to banks won't work anymore.
I think the file is named STK.apk. if I am not wrong.
On all the Stock (based) Custom Roms this operation work. But in AOKP,AOSP it doesn't. On stock based this program is White Color and after entering PIN code it disappears and log me into the bank.
But on AOKP,AOSP it is black, and it doesn't disappear it just times out after I enter PIN code.
Does anyone know a workaround or what can be the issue ? Someone mentioned that I should switch Kernel to fireopal 3.3 unofficial but that didnt work. I flashed Kernel in TWRP, maybe it should have been flashed in ODIN ?
Caligula. Peace Out
This will likely be due to a SafetyNet issue.
Where you rooted on stock? if yes with magisk or otherwise?
If you're still on aosp you can download this SafetyNet Helper Sample and see if you pass.
If you don't there are a few things you can do to pass it again.
jaannnis said:
This will likely be due to a SafetyNet issue.
Where you rooted on stock? if yes with magisk or otherwise?
If you're still on aosp you can download this SafetyNet Helper Sample and see if you pass.
If you don't there are a few things you can do to pass it again.
Click to expand...
Click to collapse
Hi , I did use SuperManRom and BatmanRom, I think they both were rooted yes, and they use Magisk 14 beta there I think.
I will try to flash an Aosp-Aokp Rom again and then try with this App you are posting. Thank you. Now I am on STOCK Samsung since I couldn't get this to work. I used KIES to go back to fabric base.
I will make a backup and then try
UPDATE : I have now flashed Lineage Os 14.1 and I haven't root and Safetynet fails. So first thing I need is root maybe ?
mrcaligula said:
Hi , I did use SuperManRom and BatmanRom, I think they both were rooted yes, and they use Magisk 14 beta there I think.
I will try to flash an Aosp-Aokp Rom again and then try with this App you are posting. Thank you. Now I am on STOCK Samsung since I couldn't get this to work. I used KIES to go back to fabric base.
I will make a backup and then try.
Click to expand...
Click to collapse
Magisk has the capability to root your phone without triggering SafetyNet but that is (at least it was for me) a pain in the ass to get it working correctly.
Another thing I did with Snapchat (also doesn't work if SafetyNet is triggered) is that I set up the App on a clean stock rom, then backed it up with Titanium Backup and installed it on the rooted/aosp/... ROM. Note: This also works if the SafetyNet check in the app is only executed when you first login.
Thanks for info
I get false on the first CPTID(something) the heaviest of the 2 checks on SAFETYNET the other one I get ok.
After I install Magisk 14.
But I am giving up. Can't really find a 100 % workaround for this.

Anyone figure out installing Netflix from PlayStore after bootloader unlock?

I would like to install Netflix from the PlayStore and have it update from there like other apps. Is this possible after unlocking the bootloader? In case it isn't clear, I don't want to sideload it so please don't suggest that.
reiriop said:
I would like to install Netflix from the PlayStore and have it update from there like other apps. Is this possible after unlocking the bootloader? In case it isn't clear, I don't want to sideload it so please don't suggest that.
Click to expand...
Click to collapse
Obvious that is possible , I have Netflix and unlocked bootloader 1 thing don't have nothing to do with the other thing
Have you done anything other than unlock the bootloader? I'm not on a custom ROM or anything, I just mixed some stock firmware so I could get fingerprint sensor in the US. I also installed a kernel that hides bootloader unlock but in the PlayStore Netflix is listed as not compatible with my device.
reiriop said:
Have you done anything other than unlock the bootloader? I'm not on a custom ROM or anything, I just mixed some stock firmware so I could get fingerprint sensor in the US. I also installed a kernel that hides bootloader unlock but in the PlayStore Netflix is listed as not compatible with my device.
Click to expand...
Click to collapse
Don't worry about that, it's working
I installed the Magisk module 'liboemcrypto disabler' on Android Pie to be able to even see Netflix in the Playstore. Now Netflix works and updates from the Playstore as well. But I can't watch content in HD.
On Oreo Netflix worked in HD and HDR mode, but I had to install a DRM fix to achieve that.
ishemes said:
I installed the Magisk module 'liboemcrypto disabler' on Android Pie to be able to even see Netflix in the Playstore. Now Netflix works and updates from the Playstore as well. But I can't watch content in HD.
On Oreo Netflix worked in HD and HDR mode, but I had to install a DRM fix to achieve that.
Click to expand...
Click to collapse
Have you tried janjan's kernel with DRMfix built in?
works with Pie
Didgesteve said:
Have you tried janjan's kernel with DRMfix built in?
works with Pie
Click to expand...
Click to collapse
Thank you for the suggestion, but janjan's kernel only has a drm fix for Oreo if I understand correctly. I don't believe there is a DRM fix for Pie available (yet). I also don't think anybody is going to spend the time needed to create one, because now that the camera works, most people don't even notice that a DRM fix is necessary.
ishemes said:
Thank you for the suggestion, but janjan's kernel only has a drm fix for Oreo if I understand correctly. I don't believe there is a DRM fix for Pie available (yet). I also don't think anybody is going to spend the time needed to create one, because now that the camera works, most people don't even notice that a DRM fix is necessary.
Click to expand...
Click to collapse
Sorry, you're right, my bad. I have been using janjan's kernel on Oreo and it's been flawless. Given the amount of negative comments about Pie, are you not tempted to go back to something that works properly?
Didgesteve said:
Sorry, you're right, my bad. I have been using janjan's kernel on Oreo and it's been flawless. Given the amount off negative comments about Pie, are you not tempted to go back to something that works properly?
Click to expand...
Click to collapse
I actually love Pie. I removed most of my rooted apps because Pie has functionality built in that I really wanted on Oreo. Like choosing dns servers, dns over https, rotation icon in navigation bar, bluetooth device battery percentage and more things I can't remember. Battery life is good.. phone is stable... My only complaints are that Sony took out some of the things that make Pie more usefull. But besides that I'm happy.
ishemes said:
I installed the Magisk module 'liboemcrypto disabler' on Android Pie to be able to even see Netflix in the Playstore. Now Netflix works and updates from the Playstore as well. But I can't watch content in HD.
On Oreo Netflix worked in HD and HDR mode, but I had to install a DRM fix to achieve that.
Click to expand...
Click to collapse
This didn't work for me, still the same issue. I also tried flashing janjan's kernel but it didn't make a difference either and the ctsProfile is still false. Does anyone know if the ctsProfile being false would cause this?
Another thing that I think is separate but strange is that I have Magiskv19.0 installed but the Magisk Manager tells me Magisk is not installed and that v18.1 is the latest version.
reiriop said:
This didn't work for me, still the same issue. I also tried flashing janjan's kernel but it didn't make a difference either and the ctsProfile is still false. Does anyone know if the ctsProfile being false would cause this?
Another thing that I think is separate but strange is that I have Magiskv19.0 installed but the Magisk Manager tells me Magisk is not installed and that v18.1 is the latest version.
Click to expand...
Click to collapse
I think something went wrong flashing your system. I have magisk installed and ctsProfile: true. I would concentrate on that first. Fixing magisk and ctsProfile will probably fix Netflix as well. Good luck!
Ya, so before I flash the tmobile volte/wifi calling zip or flash my kernel .img the ctsProfile is true and I am able to install Netflix from the play store. As soon as I flash one of those though the ctsProfile check turns to false. I need to flash these though or I'm not able to get VoLTE, WiFi Calling, and without hiding the bootloader unlock with the kernel some of the Sony features don't work.

Magisk SafetyNet fail - Android 11

I've recently encountered a problem. I rooted My Pixel 3a when it had stock Android 10 and passed the SafetyNet checks.
I then upgraded to stock Android 11 (RP1A.201005.004, Oct 2020) and re-rooted. However, the Magisk SafetyNet check now reports as 'attestation failed'. basicIntegrity passes but ctsProfile now fails (evalType HARDWARE).
Can anyone help in identifying the problem and how to resolve it?
largeruk said:
I've recently encountered a problem. I rooted My Pixel 3a when it had stock Android 10 and passed the SafetyNet checks.
I then upgraded to stock Android 11 (RP1A.201005.004, Oct 2020) and re-rooted. However, the Magisk SafetyNet check now reports as 'attestation failed'. basicIntegrity passes but ctsProfile now fails (evalType HARDWARE).
Can anyone help in identifying the problem and how to resolve it?
Click to expand...
Click to collapse
Same, passed it about a week ago and failed it today - I've had the October update since release and it has been fine so something has changed in the last few days ?
Magisk 21005
Manager 311
Cananry update channel
captain sideways said:
Same, passed it about a week ago and failed it today - I've had the October update since release and it has been fine so something has changed in the last few days
Magisk 21005
Manager 311
Cananry update channel
Click to expand...
Click to collapse
You have to use magiskhide props module. See its XDA thread.
magjir said:
You have to use magiskhide props module. See its XDA thread.
Click to expand...
Click to collapse
Thanks very much for that - I did try that but it didn't work for me - went on a few searches and this module I found elsewhere on here did work.
I just flashed it and my cts profile passes - there some interesting posts round it as well:
https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40655
Relevant: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40655
@largeruk @captain sideways
Hey, I hate to steal the thread, but I wanted to ask if either of you would please upload a copy of the Magisk patched boot image file that you used. The ones that I have been generating using MM 8.0.2 and the latest sargo factory boot image have consistently failed to boot for me and I would like an image that has been proven to work. I would greatly appreciate you help!
UPDATE
Thanks for the file! It worked for me.
captain sideways said:
Thanks very much for that - I did try that but it didn't work for me - went on a few searches and this module I found elsewhere on here did work.
I just flashed it and my cts profile passes - there some interesting posts round it as well:
https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40655
Relevant: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40655
Click to expand...
Click to collapse
THANKS!!! I recently ran into this issue and have tried the modules and changes through terminal, unrooting, flashing complete stock, but the only thing that worked was locking the bootloader. Once I had my 3a wiped and back to stock, I kept experimenting and located your fix. Magisk (cts profile) still won't pass safety net, but GPay works again (at least I could re-add cards without an error message--haven't tried to use it at a pay terminal yet) which was the whole point. I hope it's long-lasting. I can't believe more people aren't running into this issue.
@largeruk @captain sideways
Just to clarify, this is not an Android 10 or 11 issue. Newer (starting around October 22) versions of Google Play Services changed how SafetyNet works and ctsProfile fails with evalType HARDWARE.
The "Hardware Off" module no longer fixes the ctsProfile failure. I have seen mention of a new module here, but I'm not sure I trust the source: https://droidholic.com/safetynet-cts-profile-failed-fix/
Anyone have updates on this issue with the latest February Android 11 release?
madmartian said:
The "Hardware Off" module no longer fixes the ctsProfile failure. I have seen mention of a new module here, but I'm not sure I trust the source: https://droidholic.com/safetynet-cts-profile-failed-fix/
Anyone have updates on this issue with the latest February Android 11 release?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/ it does work.
Edit: there is also a link to the github in the thread so you can check the code if you wish.
Hi i flashed pixel experience on my moto g7 power and i cant get the cts profile match to not fail does anyone know how to do this

SafetyNet (CTS Profile) check fails on Poco F2

Hi everyone.
I have a rooted Poco F2 with magisk 21.2 and TWRP on stock MIUI rom 12.0.4.
I had passed SafetyNet by hiding magisk manager and enabling the magisk hide props module but literally one morning I woke up with a message from Google Pay saying the phone can't be used for transactions.
I checked SafetyNet again and it indeed failed. BasicIntegrity passed and evalType was set to BASIC but ctsProfile failed.
Since I've been trying to fix it by formatting the phone entirely, flashing the stock rom from scratch and re-applying everything but i still get the same issue. I've also tried several different fingerprints from the props module but ctsProfile check always fails.
Does anyone have any clue what might've happened? I didn't mess with any setting or allow any automatic updates when i got the fail message from Google Pay.
Thanks in advance!
moxalis said:
Hi everyone.
I have a rooted Poco F2 with magisk 21.2 and TWRP on stock MIUI rom 12.0.4.
I had passed SafetyNet by hiding magisk manager and enabling the magisk hide props module but literally one morning I woke up with a message from Google Pay saying the phone can't be used for transactions.
I checked SafetyNet again and it indeed failed. BasicIntegrity passed and evalType was set to BASIC but ctsProfile failed.
Since I've been trying to fix it by formatting the phone entirely, flashing the stock rom from scratch and re-applying everything but i still get the same issue. I've also tried several different fingerprints from the props module but ctsProfile check always fails.
Does anyone have any clue what might've happened? I didn't mess with any setting or allow any automatic updates when i got the fail message from Google Pay.
Thanks in advance!
Click to expand...
Click to collapse
That method doesn't work anymore.
try this https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.1.0
Dadovvv said:
That method doesn't work anymore.
try this https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.1.0
Click to expand...
Click to collapse
That seems to have fixed it! Thank you so much.
Is there a sub-forum somewhere where I could've been updated that the method I was using isn't working anymore?
[TUTORIAL] WORKING FIX FOR SAFETYNET / CTS PROFILE FAILED
Alright , here we go again . Steps to follow : 1. Open Magisk and select modules tab 2. Install Module for Android 11 - (https://t.me/XiaomiEUCloud/156) For Android 10 - (https://t.me/XiaomiEUCloud/158) from Storage 3. Reboot your Device Done . [emoji3544] UPDATE : NO NEED TO FLASH THIS ON...
xiaomi.eu

Question Solved - C.44 update won't install after magisk boot

Hi guys,
Sorry if I'm missing something very obvious but I can't install the latest update on my rooted oneplus 9
I have a LE2110 model, currently on 11.2.10.10..LE25BA. I'm rooted with magisk, confirmed with root checker.
I've downloaded the C44 update, went to updater, install from storage, then to magisk where I disable all my modules and select install to inactive slot, 'lets go' and 'reboot'.
The phone reboots and displays a message saying that the update did not install try again or try reapir.
Anyone know if I'm missing anything in the process? Any help would be appreciated.
Cheers everyone
Edit: Thanks for all the responses..using canary magisk instead has worked.
chinbags said:
Hi guys,
Sorry if I'm missing something very obvious but I can't install the latest update on my rooted oneplus 9
I have a LE2110 model, currently on 11.2.10.10..LE25BA. I'm rooted with magisk, confirmed with root checker.
I've downloaded the C44 update, went to updater, install from storage, then to magisk where I disable all my modules and select install to inactive slot, 'lets go' and 'reboot'.
The phone reboots and displays a message saying that the update did not install try again or try reapir.
Anyone know if I'm missing anything in the process? Any help would be appreciated.
Cheers everyone
Click to expand...
Click to collapse
You have to fastboot flash the stock untouched boot.img back. Magisk patched the boot partition to root. Therefore the partition is modified. Ota fails. Try uninstall Magisk and see if it restores stock boot image. Or get full build run payload him through payload extractor and nab boot.img there.
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
chinbags said:
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
Click to expand...
Click to collapse
Wrong magisk was used. You must use canary magisk.
MrSteelX said:
Wrong magisk was used. You must use canary magisk.
Click to expand...
Click to collapse
Wrong . I'm on stock A12 and it's rooted with 23.0. passing safety net,modules,Magisk hide all working
in order for magisk to work on A12 and booting to an inactive slot it has to be the alpha build ill post it but its also in the root guide for oos on 12 the table shows the only one that works on 12 is this build, same thing happened to me
chinbags said:
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
Click to expand...
Click to collapse
no need for any of that
mattie_49 said:
Wrong . I'm on stock A12 and it's rooted with 23.0. passing safety net,modules,Magisk hide all working
Click to expand...
Click to collapse
yes it is true but you did the manual way. every one else wants the automatic way which requires canary or alpha.
MrSteelX said:
yes it is true but you did the manual way. every one else wants the automatic way which requires canary or alpha.
Click to expand...
Click to collapse
Everyone does want bleeding edge.
Thanks for all the info guys, sounds like a bit more reading needed on my end but all of the above should steer me in the right direction.
I was able to jump from rooted 11.10.10 to c44 using canary magisk.
Downloaded the 4gb c44 from oxygen updater, then local udpate and DONT reboot then install magisk in inactive slot.
Ok, this has worked, original posted uodated, thanks everyone.
One last question...and slightly unrelated. I can't find my list of hidden apps in magisk. I've hidden the app in settings and have the magisk hideprops config module enabled. My banking app is telling me I'm rooted...I'm pretty sure I added it to a list in the past. None of the options at the bottom bring me to it either..anyone have the same issue?
chinbags said:
One last question...and slightly unrelated. I can't find my list of hidden apps in magisk. I've hidden the app in settings and have the magisk hideprops config module enabled. My banking app is telling me I'm rooted...I'm pretty sure I added it to a list in the past. None of the options at the bottom bring me to it either..anyone have the same issue?
Click to expand...
Click to collapse
the alpha build doesnt have magisk hide built in. and he literally just posted the updated v24 stable build an hour ago and is supposed to fully support android 12. but he also announced that he removed Magisk hide all together and is no longer going to support it.
so its still early, not sure how to fix your problem , those are the only two builds i see for 12
jruizdesign said:
the alpha build doesnt have magisk hide built in. and he literally just posted the updated v24 stable build an hour ago and is supposed to fully support android 12. but he also announced that he removed Magisk hide all together and is no longer going to support it.
so its still early, not sure how to fix your problem , those are the only two builds i see for 12
Click to expand...
Click to collapse
Ok, thanks. Could a rollback to v23 APK work? Happy to give it a whirl unless you think it could bork my phone
chinbags said:
Ok, thanks. Could a rollback to v23 APK work? Happy to give it a whirl unless you think it could bork my phone
Click to expand...
Click to collapse
i would try and delete the version you have and install stable 23, dont repack the boot.img or anything only replace the app, that wont hurt you
jruizdesign said:
i would try and delete the version you have and install stable 23, dont repack the boot.img or anything only replace the app, that wont hurt you
Click to expand...
Click to collapse
No dice, v23 will install and the option is available in settings, I just still can't find where I add an app to the hidden list. Bank apps not loading.
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
Have you tried using USNF? https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
I'm also having troubles updating to c44 with magisk v23, but don't wanna lose the magisk hide option. While looking for alternatives, I came across this the USNF solution in here :
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Didn't try it myself yet...
I can confirm USNF works for me, and I have some very strict apps detecting root access, DenyList hides the root from the apps, but it doesn't try to fix safetynet, with USNF I have no more problems even in apps that didn't work with DenyList only (remember to turn on Zygisk and Enforced DenyList).
If you are using permissive mode on SELinux you will also need SELinux switch to get back to enforcing mode for some apps, but that is an edge case
EDIT: It seems if you are on custom ROM MagiskHidePropsConf might help, not sure if USNF is enough but I can't test it

Categories

Resources