I'm having trouble getting SafetyNet to pass for the past 2 days or so. It fails on stock, unrooted rom, with an unlocked bootloader. It also fails with the latest Magisk. I also tried restoring a backup of /boot and /system that was passing SafetyNet a few days ago, and no luck.
Has SafetyNet suddenly stopped working for anyone else? Any tips for success?
Working fine on magisk 13.2 rooted TWRP all else stock currently.
Ok, I just tried dirty flashing OTA zip and latest Magisk 13.2 and still no luck. Will try a full reset tomorrow...
yubimusubi said:
Ok, I just tried dirty flashing OTA zip and latest Magisk 13.2 and still no luck. Will try a full reset tomorrow...
Click to expand...
Click to collapse
See the Magisk General Support Thread . There's been an update to SafetyNet and there's a temporary workaround on GitHub.
adrman said:
See the Magisk General Support Thread . There's been an update to SafetyNet and there's a temporary workaround on GitHub.
Click to expand...
Click to collapse
That did not fix it for me, but I'm glad to know I'm not the only one having issues lately. Will keep an eye on that thread.
Just to close the loop on this...
Even after a full wipe through TWRP I couldn't get SafetyNet to pass. I ended up re-locking bootloader, reflashing stock recovery and stock system, and once I confirmed it was passing, unlocked bootloader again and installed Magisk. It is working now, but no idea how my system got into such a state.
Yeah mine isn't working anymore either. Was working till I tried it last night and no go. Waiting for the 13.3 with a fix i guess
I had the same issue with magisk failing both SafetyNet checks using stock OOS 4.5.5, TWRP 3.1.1, Magisk 13.2. The fix from github which removes all build properties with "magisk" in the name worked for me (any resetprop errors can be ignored; it just means that specific property was not set).
Code:
$ adb shell
OnePlus5:/ $ su -
(accept magisk prompt on phone to allow root)
OnePlus5:/ # resetprop --delete init.svc.magisk_pfs; \
resetprop --delete init.svc.magisk_pfsd; \
resetprop --delete init.svc.magisk_service; \
resetprop --delete persist.magisk.hide; \
resetprop --delete ro.magisk.disable
After this both SafetyNet checks pass. This will be reset any time you change magisk settings, upgrade magisk, or reboot, and SafetyNet will fail again after. But you can run the same command to work around again. Haven't tried the "Universal Init.d Enabler" magisk module mentioned in the other thread, I just created a shell script with the above command and call it from from Terminal Emulator if needed.
There's no point in trying different versions, factory resetting, etc. You can either run the temporary fix posted by MonkeeSage (which worked for me), or wait for an update.
geoff5093 said:
There's no point in trying different versions, factory resetting, etc. You can either run the temporary fix posted by MonkeeSage (which worked for me), or wait for an update.
Click to expand...
Click to collapse
Agree. In my case something was totally bonk with my system to the point that none of the fixes would let it pass. I think it stemmed from a random crash that corrupted some data, and that it was just coincidence that a SafetyNet update happened about the same time. I know it sounds crazy, but nothing short of going full stock and locked then re-rooting worked. Trust me I didn't want to wipe my data so I tried everything else first.
I can confirm now that the workaround script is necessary, and works for me when run at each reboot.
@Funk Wizard put up a mention of this little apk that does the steps needed to make safetynet pass while the Google vs. US wars are on. Credits are due to @Agusyc15 ::
Here's the link: https://forum.xda-developers.com/oneplus-5/themes/app-pass-safetynet-2017-07-17-magisk-v13-t3638444
Magisk has been updated to 13.3 and has fixed the SafetyNet failing caused by the last update from Google.
Magisk 13.3
Confirmed working for me.
13.3 works for me too.
Yep all good here as well.
13.3 sorted my issues
Guys what is the safest way to install magisk 13.3 on our op5 so it passes android pay, gets op5 ota updates, etc?
Btw I dont flash twrp, I usually just boot into twrp from fastboot. That shouldnt make a difference right? I havent even unlocked this device yet.
LOL
My SafetyNet has failed this morning when checking.
Was perfectly fine yesterday morning, once updated to the 13.3 build.
L22EEW said:
LOL
My SafetyNet has failed this morning when checking.
Was perfectly fine yesterday morning, once updated to the 13.3 build.
Click to expand...
Click to collapse
Have you installed Magisk 5.1.1? This fixes it. Google seem to be really cracking down on.it though in general.
Batfink33 said:
Have you installed Magisk 5.1.1? This fixes it. Google seem to be really cracking down on.it though in general.
Click to expand...
Click to collapse
I have, as I had a OTA update for Magisk app this morning. When I updated the app, I carried out a SafetyNet check - which failed.
Grrr..
L22EEW said:
I have, as I had a OTA update for Magisk app this morning. When I updated the app, I carried out a SafetyNet check - which failed.
Grrr..
Click to expand...
Click to collapse
That's strange, 5.1.1 with 13.3 works fine for me. It didn't before 5.1.1.
Related
Hi all,
Not even sure I'm in the right place, still I'd like to share my own experience after upgrading to Oreo last few days. So moderators, if you guys find this irrelevant, or it is in the wrong place, please help me move it accordingly.
I am using XZ F8332. Last few days I decided to say hello to Oreo after some time being patient with the pretty annoying "Upgrade your system" notification. I finally managed to have a fully working Oreo + DRMfix + Magisk + SafetyNet passed and root. Unfortunately good things usually come with bad things too...
At first, I was trying to patch my boot image using ta_poc method. Believe me ta_poc seems to be working on Oreo too, I got all the DRM functionalities working thanks to munjeni & serajr. However, it doesn't seem to be working with both Magisk and SuperSU. I tried all recent versions of those two e.g. Magisk v14, Magisk v14.5 beta, SuperSU v2.79 SR3, SuperSU v2.82 SR5, etc... ALL cause bootloops! I had to come to a conclusion that any methods that patch your modified (with ta_poc) boot image will cause bootloops. There's one thing I didn't try: SuperSU system mode which installs to /system. What's the point of system-less then? But it's up to you to try this.
The above means you are most likely gonna lose root if you go with ta_poc on Oreo. So I had to give ta_poc up and go with DRMfix instead. I got into a few troubles then.
I was initially trying to keep my userdata intact, so I didn't do a full wipe, I actually wiped everything except only my userdata (including data in sdcard). DRMfix didn't fix at all. All I got was only "FIDO_KEYS: Provisioned", the rest was "general error!" and of course DRM functionalities didn't work. I did some search, followed some guides saying about removing these directories: /data/credmgr, /data/drm and /data/mediadrm. There's even a script named "SafetyNet-Cleaning-Tools" also does exactly the same. Perhaps I wasn't that lucky enough. It just didn't work. Until I had to pull all of my data out, do a FULL WIPE including userdata, DRMfix worked then.
Next thing is to get Magisk (or SuperSU) working to have root. I knew recent update of SuperSU causes Xperia devices into bootloops. I also used Magisk on Nougat too. Why not now? So I flashed Magisk v14. Uh oh... I met my old dear friend again, Mr. Bootloops. So Magisk v14 doesn't work on Oreo. But v14.5 beta does. That's how I got it fully working.
Then I pushed my data back to sdcard (including a nandroid of course), did a restore DATA ONLY in TWRP and manually delete the folders mentioned above. After phone started, everything went back. I smiled.
Some existing Magisk modules started to work without any problems. But some other they need busybox. Without any thoughts, I immediately installed osm0sis' busybox installer, the one on Magisk repo. Weirdly it said "Magisk is not activated". I tried other modules, same issue. So only existing modules work, I couldn't install any new modules using Magisk Manager. "Use TWRP then" I thought. I went to TWRP and flashed the busybox installer. My old dear friend came and said "Hi! Bootloops!!" to me again. This time I used Magisk uninstaller to clear magisk files and re-flashed it again. I was able to get back in. I tried YashdSaraf's busybox universal installer. Same issue. Maybe I haven't tested well enough or maybe I went completely wrong way, but looks like busybox isn't working on Oreo? Also, I'm not sure this is the right way to do it, or we have to "clean install" Magisk too? Like uninstall everything first and re-install module by module all over again?
Also, after some Magisk uninstalls and reflashs, suddenly my DRMfix was no longer working. It displayed "general error!" in Service tests -> Security. I tried to fastboot the modified boot image again. Not working. There's no way to get it back except a FULL WIPE. I didn't get it. System-less approach is supposed to have nothing to do with our files. Somehow it does leave some traces, which we need a FULL WIPE to get rid of it? Maybe it isn't just the 3 folders mentioned above, there's maybe more?
Additionally, on Oreo I got some other bad stuffs:
- Adaptive brightness keeps adjusting, going darker and brighter very very quickly. It's no doubt an Oreo's bug.
- Cannot open Titanium Backup. It crashes right after you open it. I tried v8.0 and v8.1. Same issue. Maybe it's because busybox isn't installed?
- I have a feeling battery drains issue comes back. Looks like its consuming more battery than latest Nougat I'm not sure. Haven't got time to do some stats yet.
Last but not least. When I was pulling / pushing data to / from, I noticed that the storage space somehow changed! My phone is 64gb but the second time I got it fully working, it said "storage is 80% full..." and when I opened Settings -> Storage it showed only 21gb! What I did to get it fixed was to run fastboot format userdata. Then I let the phone start normally (without old data), after finishing setup, I turned off and went to TWRP to restore DATA ONLY. Problem solved. I got my storage back. But I have never figured out why. Maybe something wrong with adb pull / push in recovery?
If you've read down this far, I hope my experience could somehow help you avoid encountering the problems that I did.
Me personally I think I will go back to Nougat and stay low for a while. You understand why. Another reason is I also wanna try the "official" xposed for nougat for a little more. rovo89 is freaking awesome. man, he's a legend.
References:
I used this tool to patch my boot image (kernel). This tool origins by tobias.waldvogel but I used the "unofficial" one here and here modified by serajr for the ta_poc method. Thank you guys for this amazing tool.
Magisk latest versions here
SuperSU v2.82 SR5, v2.79 SR3
SuperSU System Mode v2.82 SR5 here
osm0sis' Busybox installer here
YashdSaraf's Busybox universal installer here
Special thanks to serajr, juanpirulo, munjeni, rovo89 and tobias.waldvogel for your amazing works & supports. I dont tag you guys here coz I dont wanna bother you guys
Been there... I feel like that phone don't want to work with poc and Magisk...
FakeMobile said:
Been there... I feel like that phone don't want to work with poc and Magisk...
Click to expand...
Click to collapse
ta poc needs to be rebuild, but munjeni probably dont wanna work in his tool anymore. But serajr´s tool works well so you can root xz oreo with magisk. cheers
Yeah it what I have atm, but I still can't mirror cast to my tv because it not real drm keys
Take a look here: https://developers.google.com/android/images
Download it now!!
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)
ApoelEllhnwn said:
Install manually and everything works perfect (Magisk 17.1, twrp 3.2.3-1)
Click to expand...
Click to collapse
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.
wish someone would make the factory images Flashable. All this needing a computer to update is getting old!
Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I'm sorry I must not have been very clear. My ask was for someone to try the process detailed in the link I provided in my quote above. This is supposed to allow you to uninstall Magisk (don't reboot), take the OTA as you normally would on unrooted phone, and once it installs, apply Magisk to the new slot w/ the OTA installed, then reboot. No computer needed. As I stated above, I would do it, but have yet to get the update thru the Check System Update. I am well aware of how to install it manually, as I have done that process for every update. I just saw that the linked process was updated for Magisk 17.0+ and hoped it could be verified to work. Meaning this would simplify the monthly update process tremendously.
kolothuk said:
I installed the Pixel 2 Update manually (walleye-ppr2.180905.005-factory-4895938f.zip) using this guide.. Followed by twrp-3.2.3-1-walleye and Magisk 17.1. Everything seems to be working fine.
Click to expand...
Click to collapse
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.
kittygotwet said:
Hey, I'm following this guide to a T. But whenevever I push to install magisk, it fails.
Any idea?
flash-all
reboot to bootloader -> flashboot boot twrp -> push magisk to tmp -> push twrp.zip to tmp -> install magisk and it fails.
Click to expand...
Click to collapse
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.
davidisflash said:
Just install the latest Magisk 17.1 zip in twrp. You don't need to push anything. It works fine for me.
Click to expand...
Click to collapse
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.
kittygotwet said:
I tried doing that too and it's failing, my build number and the file I downloaded from Google to flash-all matches. I'm not sure what's going on.
installing from twrp is giving me an error 2.
Click to expand...
Click to collapse
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.
davidisflash said:
Are you using the latest twrp that was released end of August? I did and simply did fastboot boot <twrp image file>. Then right away in TWRP, instead of installing TWRP with the TWRP zip, I simply flashed the Magisk 17.1 zip. That's it. Done.
Click to expand...
Click to collapse
I actually figured it out. I had to use the Magisk uninstaller to remove any remaining Magisk, I guess, before I can reinstall. Now I just have another issue on the Pixel 2 9.0. Converting any user app to system app corrupts the phone.
Duhman72 said:
Is anyone willing to try this to see if it works? I haven't gotten the update thru the Check for Update button in the system menu yet or I would try it. It never worked in the past but it seems they have updated this method to work w/ Magisk 17.0+. If i don't get the update by tomorrow evening, I will just install the factory image manually like i do every month.
Magisk OTA installation
Thanks in advance!
Click to expand...
Click to collapse
I will try this guide as soon as the OTA is available.
I got another update today on my Pixel 2, which said: critical bug and performance fixes... I wonder what it is? The phone isn't as smooth after this and some glitches with youtube in landscape, there white nav bar appears, but I can't click 3 dots menu to adjust quality for example. I have to turn the phone in portrait and then do it.
razorsbk said:
I will try this guide as soon as the OTA is available.
Click to expand...
Click to collapse
I'm also still waiting for the Update ...is that normal to wait that long time?
No, it's not. Other manufacturers have released their patches via OTA.
Sent from my Pixel 2 using Tapatalk
So you think we have to sideload the patch?
How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?
Ashyford said:
How can I add the latest security updates to my Pixel 2 running 8.1 without transitioning to 9.0?
Click to expand...
Click to collapse
You can't. Google is no longer releasing OTAs for 8.1. Your best bet is to use a custom kernel such as FlashKernel, as I believe it is backwards compatible, and Nathan streamlines the security patches from both Google and the Linux kernel fork into his kernel.
Did anyone else got the OTA ? I'm still wainting
I was running stock 7.1.1 and everything was fine. Then i decided to try LOS 15.1, with magisk 17.4 but encountered an issue with safetynet cts profile false that prevented me from using android pay. I then proceeded to flash B35 EDL, and then do the sd upgrage to Oreo B20, but i still have the same issue with failing cts profile.
AI'm no longer rooted, running stock but still fail safetynet. Any one have any ideas what I can try next? at this point i just want cts profile to pass on the current oreo b20 stock.
Thanks!
It could be that SafetyNet detects that you have an unlocked bootloader, but there are ways to hide that (custom kernel, Magisk, etc). Do you have Xposed installed? That's an automatic SN fail. You haven't changed system partition in any way at all? It's also possible that Google hasn't yet approved B20 despite it being official rather than beta. There could be other factors too. SN looks at lots of things, many of which Google won't talk about.
You need to install magisk hide props and then in a terminal
"Su"
Grant superuser
Then
"Props"
And follow the on-screen instructions. Stupid that Google pay has a problem with rooted phones as it's painfully simple to get around it
You can find magisk hide props in the "download" section of magisk manager
Check the settings in the Google play store, Device not certified can be an issue when you change Roms.
The link between the device and Google has been broken, hence the device not certified.
There is an app Device ID that can add the certification back to its original state.
Hope this helps
Turned out to be it was because of the unlocked bootloader.
funny story... i locked the bootloader without having oem unlock enabled . Got bricked, couldn't boot into EDL... so i had to take it apart and ground the test point to put it into EDL.
xavoc said:
Turned out to be it was because of the unlocked bootloader.
funny story... i locked the bootloader without having oem unlock enabled . Got bricked, couldn't boot into EDL... so i had to take it apart and ground the test point to put it into EDL.
Click to expand...
Click to collapse
There's a tool for that now; you may not have had to open it: https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
TPMJB said:
You need to install magisk hide props and then in a terminal
"Su"
Grant superuser
Then
"Props"
And follow the on-screen instructions. Stupid that Google pay has a problem with rooted phones as it's painfully simple to get around it
You can find magisk hide props in the "download" section of magisk manager
Click to expand...
Click to collapse
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.
xavoc said:
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.
Click to expand...
Click to collapse
try this thread https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809/page2
Update to Magisk v17 and then try the above solution
xavoc said:
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.
Click to expand...
Click to collapse
"Magisk hide props config" is literally what it is called. If you can't find it, you're doing it wrong.
If all else fails, google then install manually.
Had to upgrade to magisk 17 to see the hide prop module download. Still couldn't pass safetynet with Oreo B20. Switched to LOS 15.1 and now everything works.
We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....
gaww said:
We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....
Click to expand...
Click to collapse
No, the betas don't wipe...at least not for me, I downloaded DP3 and installed it as local update, afterwards flashed DP3patched.img boot_a and _b and root is fine without any loss of data...
gaww said:
We are getting close to a new Android version, and waiting on global version 10.5.13 - but with only minor tweaks in the change list, is it worth doing.
If you're stock, no problem, but with root, TWRP, magisk, and mods - why bother? After last update, screwed up restoring TWRP and had to setup everything again.
As for updates - when the final new non-beta comes out, will it wipe every like the betas ?
The betas wipe because OnePlus wants clean installs to get responses on the ROM not caused by other issues. But not so with the finale one....
Click to expand...
Click to collapse
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.
Nope, DP3 does not force formatting data. I'm very happy with DP3. Dual SIM support in the US and I have root.
Menoobone said:
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.
Click to expand...
Click to collapse
Does it have to be Magisk Canary ?
gaww said:
Does it have to be Magisk Canary ?
Click to expand...
Click to collapse
Yes for now...
Menoobone said:
I went from 10.5.10 to 10.5.11 to 10.5.12 without any issues though. TWRP and Magisk still stick, likewise my V4A and xXx modules.
I also had a chance to try the beta 3 and no, it doesn't wipe the phone for me. The only issue is that some modules like v4a don't work but patched TWRP and Magisk Canary do stick.
Click to expand...
Click to collapse
Another question - is there another way to move back down without MSM - which wipes - as well as unlocking also. ?
[GUIDE] HOW TO UPDATE TO RUI 2.0 AND ROOT IT
--> Disclaimer: I'm not responsible if you brick your device. Use at your own risk and always backup your data! <--
0. Download linksF.14 OTA: Download
Magisk app: Download
OrangeFox beta: Download
ADB/Fastboot tool: Download
Patched boot.img: Find attached
vbmeta.img: Find attached
Patched safetynet fix: Find attached
1. Update your deviceUpdate your device to the latest firmware version (F.14). Therefor flash the provided OTA zip via stock recovery or OrangeFox beta recovery.
It is recommended to use the stock recovery. You can also update your device to the latest firmware by using the build in update function.
2. Root your deviceBoot into fastboot mode. To boot into fastboot mode, shut down your device and then press the volume down button while clicking on the power button.
Now you have successfully booted into fastboot mode. Connect your device with your computer and flash the patched boot.img and also disable verified boot.
Therefor just type following 3 commands:
1. fastboot flash boot patched_boot.img
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot reboot
Your device should boot up. Now install the Magisk app and you have successfully rooted RUI 2.0.
3. Fix SafetynetInstall the patched "safetynet-fix-v.2.2.0-zip" module via Magisk. It will fix safetynet (Basic integrity and CTS). It works perfectly and won't brick your fingerprint etc. Thanks to @osm0sis
4. Get Widevine L1If you have unlocked your bootlader, Widevine will be set from L1 to L3. This will reduce the quality of certain streaming apps like Netflix from FullHD to SD quality.
However, you can get Widevine L1 back by contacting the Realme support. For more info, check the guide from @hack-os: Widevine L1 FIX
Reserved
DarkImperator said:
3. Fix Basic integrity check (Safetynet)Unfortunately, it is not possible to pass safetynet with rooted RUI 2.0. However, you can still pass basic integrity, which should be fine for most banking apps.
To do so, open the Magisk Manger app and click on the settings button on the top-right corner. Enable "Zygisk" and "Denylist". Then click on "Configure DenyList".
Click on the 3-dots on the top-right corner and select system-apps. Now search for "gms". You should find "Google Play Services". Click it and enable "com.google.android.gms" and "com.google.android.gms.unsuable". Now reboot your device and it should pass basic integrity.
Click to expand...
Click to collapse
I have rooted with magisk alpha and my snet passed easily.
To pass snet using magisk alpha:
1. Keep zygisk disabled.
2. Enable MagiskHide.
3. Configure DenyList for "com.google.android.gms" and "com.google.android.gms.unsuable" then reboot and done.
Eng.Raman said:
I have rooted with magisk alpha and my snet passed easily.
To pass snet using magisk alpha:
1. Keep zygisk disabled.
2. Enable MagiskHide.
3. Configure DenyList for "com.google.android.gms" and "com.google.android.gms.unsuable" then reboot and done.
Click to expand...
Click to collapse
Thanks for the info. I already tried it once with Magisk Alpha and the same settings as you, but CTS still failed. I'm gonna try it again and update the guide.
Edit: @Eng.Raman Unfortunately, it doesn't work. Installed Magisk Alpha, also cleaned all data of Google Play Store and Google Play Services multiple times and rebooted multiple times. But CTS still fails.
Do you maybe have installed some modules, like Riru or LPosed?
DarkImperator said:
Thanks for the info. I already tried it once with Magisk Alpha and the same settings as you, but CTS still failed. I'm gonna try it again and update the guide.
Edit: @Eng.Raman Unfortunately, it doesn't work. Installed Magisk Alpha, also cleaned all data of Google Play Store and Google Play Services multiple times and rebooted multiple times. But CTS still fails.
Do you maybe have installed some modules, like Riru or LPosed?
Click to expand...
Click to collapse
Don't dirty-flashing alpha over canary. completely uninstall magisk canary then clean install magisk alpha.
Yes ,I have installed some modules but they don't affect the test result, even without magisk and lsposed modules I have passed snet.
Eng.Raman said:
Don't dirty-flashing alpha over canary. completely uninstall magisk canary then clean install magisk alpha.
Yes ,I have installed some modules but they don't affect the test result, even without magisk and lsposed modules I have passed snet.
Click to expand...
Click to collapse
Yes, I know. That's exactly what I did. I uninstalled Magisk Canary completely including the app and went back to stock boot. Afterwards I installed Magisk alpha app, patched boot.img, flashed patched boot.img an rebooted.
Just a couple of minutes ago a new version of magisk alpha was released, and also with that version CTS fails.
Nevertheless, I found out something interesting. With Magisk Canary, CTS fails and Advice tells me to Lock bootloader. With Magisk Alpha CTS still fails, but I get no advice.
DarkImperator said:
Yes, I know. That's exactly what I did. I uninstalled Magisk Canary completely including the app and went back to stock boot. Afterwards I installed Magisk alpha app, patched boot.img, flashed patched boot.img an rebooted.
Just a couple of minutes ago a new version of magisk alpha was released, and also with that version CTS fails.
Nevertheless, I found out something interesting. With Magisk Canary, CTS fails and Advice tells me to Lock bootloader. With Magisk Alpha CTS still fails, but I get no advice.
Click to expand...
Click to collapse
What is your Momo app and magisk Detector results? Can you screenshot ?
Eng.Raman said:
What is your Momo app and magisk Detector results? Can you screenshot ?
Click to expand...
Click to collapse
Yes. Have installed both and attached the screenshots. Have not added any of those apps to my DenyList.
DarkImperator said:
Yes. Have installed both and attached the screenshots. Have not added any of those apps to my DenyList.
Click to expand...
Click to collapse
Your momo app shows " The environment is broken" and this is related to enabling MagiskHide.
To get rid of this message and to see full results either add config "app_zygote_magic" or install momohider-mod zip attached.
Eng.Raman said:
Your momo app shows " The environment is broken" and this is related to enabling MagiskHide.
To get rid of this message and to see full results either add config "app_zygote_magic" or install momohider-mod zip attached.
Click to expand...
Click to collapse
EDIT: @Eng.Raman had to install MomoHider and add config "app_zygote_magic". Now Momo gives me the message.
DarkImperator said:
Installed MomoHider, but it still said "The environment is broken". So I disabled MagiskHide. Only as MagiskHide was disabled, I received a message from Momo. Screenshot attached.
Click to expand...
Click to collapse
That's weird you can't even hide magisk and su file.
Eng.Raman said:
That's weird you can't even hide magisk and su file.
Click to expand...
Click to collapse
Yeah, Magisk alpha seems not to fix CTS on my device. Safetynet-fix (https://github.com/kdrag0n/safetynet-fix) does, but it also bricks my in-display fingerprint reader. So at the moment it seems like I can't bypass CTS.
DarkImperator said:
Yeah, Magisk alpha seems not to fix CTS on my device. Safetynet-fix (https://github.com/kdrag0n/safetynet-fix) does, but it also bricks my in-display fingerprint reader. So at the moment it seems like I can't bypass CTS.
Click to expand...
Click to collapse
My fingerprint also works well.
Are you tried to pass the snet with the latest USNF-2.1.2? May it works for you.
Eng.Raman said:
My fingerprint also works well.
Are you tried to pass the snet with the latest USNF-2.1.2? May it works for you.
Click to expand...
Click to collapse
Yes, USNF and safetynet-fix both brick my in-display-fingerprint.
With Magisk alpha/canary there is no issue with my fingerprint.
DarkImperator said:
Yes, USNF and safetynet-fix both brick my in-display-fingerprint.
With Magisk alpha/canary there is no issue with my fingerprint.
Click to expand...
Click to collapse
Try clean installing magisk custom it has MagiskHide without DenyList, builtin snet checker and online modules repo as magisk stable, the latest custom magisk build is 23015.
Eng.Raman said:
Try clean installing magisk custom it has MagiskHide without DenyList, builtin snet checker and online modules repo as magisk stable, the latest custom magisk build is 23015.
Click to expand...
Click to collapse
What exactly do you mean with Magisk custom? I was not able to find other 23015 builds than from topjohnwu and vbb2060
DarkImperator said:
What exactly do you mean with Magisk custom? I was not able to find other 23015 builds than from topjohnwu and vbb2060
Click to expand...
Click to collapse
TheHitMan7 Custom Magisk ( Github Link ) updated 6 hours ago.
Also he has two TG channles one named as "Magisk Custom" for downloading the debug builds and the 2nd one named as "Custom Magisk" for supporting and discussions.
Eng.Raman said:
TheHitMan7 Custom Magisk ( Github Link ) updated 6 hours ago.
Also he has two TG channles one named as "Magisk Custom" for downloading the debug builds and the 2nd one named as "Custom Magisk" for supporting and discussions.
Click to expand...
Click to collapse
With enabled Magisk Hide it will fix basic integrity check, but not CTS. And it also bricks my in-display-fingerprint. Guess I'll stay with Magisk Canary, till there might be an update to fix those issues.
Hello guys.
When trying to add my bank card in google pay, I have an error that this phone can't be used to pay because it's rooted.
jalal.sy said:
Hello guys.
When trying to add my bank card in google pay, I have an error that this phone can't be used to pay because it's rooted.
Click to expand...
Click to collapse
I have the same issue with my banking app that doesn't allow NFC payments even though I've done everything to hide root.